I'm also -0 to branch off early, as I think it's a missed opportunity to get core devs to stick to soon-to-be-released 3.10 for as long as possible (and therefore oh-so slightly increase the chance of core devs stumbling on a bug he/she can fix prior to release :) ) .
On Mon, Oct 14, 2019 at 4:02 PM Jürgen E. Fischer <[email protected]> wrote: > On Mon, 14. Oct 2019 at 09:14:58 +0200, Denis Rouzaud wrote: > > Hi all, > > > > I don't have a strong opinion, but it would be good to have pros and cons > > to decide. > > > > Jürgen, since you are the release manager, are you saying it's not a good > > idea (why?) or rather that you have to modify the procedure (meaning more > > work)? > > The only gain I see is that we can just continue working on master earlier. > > Branching off also means that we have to put the new version number on that > branch prior to the actual release. The nightly build scripts will not > expect > to see a new branch and handle it like it as if it was a new release. > When to > merge and how to update translations in the meantime is also unclear > (transifex > is tied to the branches we current have). > > > > Jürgen > > -- > Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 > Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 > Software Engineer D-26506 Norden > https://www.norbit.de > QGIS release manager (PSC) Germany IRC: jef on FreeNode > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
