Stas Bekman wrote:
in case you haven't noticed i've posted an RC, so we enter the code freeze phase. So please avoid committing code changes, unless they are fixes of something that's broken (e.g. tests).
I think we may want to change that practice in order not to create obstacles for new development. We should TAG the release candidate as a release and then move the tag if some post release candidate fixes should be included. I'm not sure why Doug didn't like that idea in first place.
Well, personally, I am not a fan of moving tags. Why not just make a short lived branch for release-candidates? The small fixes that apply to it can be contained to that branch. Then later merged back to the HEAD by the release manager of that RC once it's ready for release?
-- -------------------------------------------------------------------------------- Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5 http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
signature.asc
Description: OpenPGP digital signature
