On Fri, Jan 11, 2013 at 04:53:25PM +0100, Giuseppe D'Angelo wrote: > On 11 January 2013 15:21, Olivier Goffart <oliv...@woboq.com> wrote: > > c. Critical fixes (P1/P0): security, crashes or data corruption. > > Aren't important fixes (such as security fixes) good candidates for > the release branch instead of stable? > olivier's summary does not consider the release branches at all.
the active existence of release branches is temporary. their activation (merge from stable) needs to be announced a day or more in advance (so stuff important for the release is not still integrating to stable while the branch is updated). they get deactivated again after a release. as such, the release branch submission policy is a special case of the stable branch submission policy. the above point c is certainly a good starting point. _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
