-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/13 16:41, R. David Murray wrote:
I asked about this on IRC and was told that 3.2 is now a standalone branch like 2.7. Security fixes will be applied by the release manager only, and Georg doesn't see any point in null merging the commits.
Could this be written somewhere?. For instance, how the release manager must be notified about a potential relevant changeset for his/her branch.
Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQCVAwUBUaZaBplgi5GaxT1NAQIS+QP/cd7KQ/RFaqK8U9AkMG9RuyoSHVJ9f00t VuQY+UdzkhomJQez1viEWmP+9c3MMFTHtQFB3mxmZHNHoALUH1ct5DYVjPghkA6h TsZSfZsCdvU0q9sPEjYXHOgF9LGtQCZgGzqlDl5zHzWTEFXxxLmritiSiZbvFhY/ cvAspNvbnBI= =iaDN -----END PGP SIGNATURE-----