[Qgis-developer] Post-release period of portable commits only?

Sandro Santilli strk at keybit.net
Sun Feb 23 07:09:32 PST 2014

On Sun, Feb 23, 2014 at 08:36:07AM +1100, Nyall Dawson wrote:
> On 23/02/2014 7:33 am, "Larry Shaffer" <larrys at dakotacarto.com> wrote:
> > How about for a set period of time, only commits that devs think can
> > readily be ported to the 2.2.0 branch are 'allowed' on master? With any
> > code changes, which would make porting changes/fixes over to the 2.2.0
> > branch difficult, submitted via pull requests. Maybe for two weeks?
> >
> As much as I'd love to see the multithreaded rendering branch land asap,
> I'm in favour of Larry's proposal.

Needless to say, I'm also in favour of it.

It would be interesting to look at the bug tracker to check
how many bugs are reported affecting 2.1.0 in a week.

Speaking of which, there's no "2.1.0" field to pick for
the "Affected version" field in a new ticket.


More information about the Qgis-developer mailing list