Re: 4.1.0 Final RC

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > (a) RC a-la what we had until now. It will usually be in the range of weeks. i'd suggest a list where a branch is announced lets say a week before branching. i often have a few things lying around that should be in the next final but aren't commited yet. i suppose that lots of us (developers) would commit our stuff before branching if there would be such an announcement (yeah, i know .. mailinglists .. but i don't want to have to search). > (b) Once we feel enough bugs have been fixed, a final RC is created. For > this RC, only *critical show stoppers* are fixed. That is, even bug fixes > are not MFH'd unless they're for critical bugs. If a critical show stopper > is found, a fix should be merged to the RC branch, and a new Final RC > should be released. > > So, for the developers amongst you - please do not MFH anything before > discussing it on php-dev and convincing everyone it really fixes a critical > bug. what about a qa-guys only cvs mirror for the 'final-rc' where the patches have to be submitted and discussed ? > just be me being high on this Finnish Kossu :) cheers :) harald -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBO/q9N61+myS9SSHxEQJ82gCg4G27EvHHzm/Eo1TeTPl3t5VC7g4An1KV X24O/vSbB0Dyf0K7JR182Hom =BWUR -----END PGP SIGNATURE-----