> > > > 6 month dev (including ~1 month freeze) -> release -> 1 month post > release > > freeze -> release a bug fix release if needed -> move on. > > 7 months is not good as that would move the schedule into undesireable > areas > (like holidays) over time.
I understand. Then why not go with 4 (1 month freeze) 1 month post release freeze. There only adds the extra month on the end to fix anything that might come up after that is bad. > > > Packaging for each platform is up to that maintainer but that should be > > automated as much as possible really otherwise making releases is too > hard. > > Um, but I've spoken to most of the debian, ubuntu, ubuntugis, windows > maintainers and they all agree with me - I think they already have don't a > good > job to automated it a good deal, but it's still not fully automated and > therefore they are not comfortable with doing it again and again. ;) > > Of course I don't want to create heaps of more work for people but if cutting a release is a hard process then it really creates a sticky point in all this. We need to be able to release as easy as possible. What are the main problems/stoppers with having it fully automated? Do we need resources, VMs for each platform, etc? - Nathan > > > 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 > http://www.norbit.de > QGIS PSC member (RM) Germany IRC: jef on FreeNode > > -- > norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH > Rheinstrasse 13, 26506 Norden > GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
