Update queens specs from 'approved' to 'implemented' or to
rocky/approved or to untargeted, define the redirects, and
make appropriate changes on the supporting pages.
Change-Id: I48aa6a2f11831ffc544e8b02b0bfdb80aa51d3e2
Adds the Queens priorities list. Also moves the old priority lists
to their own archive page in order to de-clutter the specs landing
page.
Change-Id: I4b54f689575f3420ccc78670d71b26a8fe25f9f3
Formalize the priorities discussed at the February PTG and revised
during the April virtual midcycle meeting and at the May Summit/Forum.
Change-Id: I7f252ce0a6c634116b5afad40cba0d732eacfc61
For this cycle, I believe we should be more strict on what is/isn't a
priority. Considering the latest feedback from the community and our
current team, we ought to be very careful.
This list does not exclude other works. It just clarifies what
the teams priorities are and where most of the time should probably go.
Also, this list does not define features and it doesn't replace specs.
Specs *must* be written and they'll be referenced in this list.
Change-Id: I312d0dcd815da10f083f2fb2a673f7c192c231f4
ghanshyam mann