Kevin A. McGrail wrote on 20/08/22 6:00 pm:
A pre-release doesn't require RTC so I'd suggest we either 1) use CTR and a
pre-3 *or* 2) I'd be +1 for RTC and a rc1.
Also, Giovanni and I did a pass on the announcement at
https://docs.google.com/document/d/1BGFFfZlQxYe9-H9AyEY_MVski_VtAaTb-4BLA_exwYs/edit
and it's ready we believe. The word wrapping will need work when it's brought
back to ASCII, sorry.
Ok, I'll do the wrap and ASCII conversion on the announcement now.
The upgrade file is much longer and Giovanni's done a great job with 19
pages(!!) of upgrades. I've only wordsmithed through the first few pages if
anyone has some cycles to help make it better. Sorry, the conversion back to
ASCII and word wrapping will be a pain here but best done when the editing is done.
My reasoning about RTC and pre3 went like this: It isn't a release candidate
unless it has everything done for the release, including the UPGRADE and
announcement files. However, I think we are done with everything we want to have
in the code, so I am calling for a freeze now so nothing new and unexpected gets
casually added while those two document files are finished.
If you are happy with the production testing you have been doing and the UPGRADE
and announcement files are done, when code freeze starts I'll go straight to
cutting rc1, skipping pre3. Otherwise, to make it convenient for testing I'll
package the frozen code as pre3 and make rc1 as soon as those two files are
ready. Either way, I think we are at a good point for a code freeze.
BTW, my concept of RTC is that it is a code freeze that doesn't apply for
changes that are only to documentation or comments.
