My quick thoughts from a lurker/packager who hasn't been paying attention much.
Planning a release date seems unwise. Structurally, that leads to rushing. If you really mean January 29, I think you should put the release branch in feature freeze (bug fixes, doc fixes) on November 29 and cut a beta, and then on December 29th cut an rc, with the rule being changes only for regressions from the last stable release, and then *actually follow the rule*. I have seen many projects not really take pre-release freezes seriously enough. If you violate the freeze, then I think you need to push the release date out to T+30days. I see talk of 2.0, but I don't see planned breaking changes. So I am befuddled by the grand plan. Perhaps it is to denote "all available chips tested", in which case the NEWS should be very clear about that vs breaking changes. As for 1.9.0, it's unclear if that is meant to be a departure from the stability of the previous 1.N releases. If it is, it should be 1.99.0, which is code for alpha towards 2, whereas 1.9.0 is a normal release number. _______________________________________________ flashrom mailing list -- [email protected] To unsubscribe send an email to [email protected]
