22.01 ETA still holding up?

[jimp]

@johnpoz said in 22.01 ETA still holding up?:

@stephenw10 isn't that what the future tag is for? I do recall seeing beofre target of just future.

The -next tag is for items that are potential candidates for the immediate next release. Rather than keep kicking the same set of issues forward over and over this gives us a pool of near-term goals to draw from without committing to a specific release. The Future value is for more long-term items or items that are unlikely to be completed by internal developers, but are waiting on community contributions.

[johnpoz]

@jimp thanks for the info, that makes sense.

[SteveITS]

My post yesterday was intended as tongue-in-cheek. Microsoft ran into this same discussion with Windows 10, after switching from three feature updates a year to two, then changing the labeling from "1909" to "20H2" because people kept expecting releases in March and September, per the numbers. It seems the misunderstanding here was that the ".01" release would definitely be out in January, not "when it's ready."

Changing versioning to "21Q1" may not work with internal version numbering. I don't know if "21.1" for the first release of the year then "21.2" and "21.3" would still fit the stated goal of dating the release but might be a compromise. If one is even needed...setting the "when it's ready" expectation a bit better would be another method.

I do understand the point of view where people may have been waiting for the new version to ship routers, and sympathize.