A couple of thoughts from a non-dev looking inwards: > Sorry I do not agree here: we had many cases of fixes breaking other stuff Would not something like Unit Tests help ameliorate that? That's what they're designed for isn't it? I realise the state of QGIS' unit test infrastructure isn't optimal currently, but I thought I saw a project to fix get funding recently.
> : what is blocking for an user is not relevant for another. I have customers > and friends that cannot upgrade to various versions for very specific bugs. Then why not fix the bugs and require them to be backported? I know that seems flippant, but is there a reason that backporting by the submitter/committer can't be required for any bugfix submitted? If a bugfix breaks other stuff, then either the bugfix should be regressed or the breakage fixed with another fix. Neither of these suggestions would require any outlay from the QGIS core fund, though they may increase the cost of any individual feature/bugfix. I believe GeoServer does both of these and has a healthy 30-day release schedule consisting of up to 3 branches despite having considerably fewer resources than QGIS. Just my 2p. Cheers, Jonathan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paolo Cavallini Sent: Monday, November 10, 2014 9:59 AM To: [email protected] Subject: Re: [Qgis-developer] Stability (2.8 LTS) vs development (3.0), a proposed way forward -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 10/11/2014 10:56, Nathan Woodrow ha scritto: > IMO we don't need "resources" to do bug fixing. The dev that does the > bug fix in master can do it in the 2.x branch for that stable release > if Sorry I do not agree here: we had many cases of fixes breaking other stuff, so backporting should be done with great care, and lots of extra work; that's why I believe that without significant resources we are not going to solve the problem satisfactorily. All the best. - -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRgjH0ACgkQ/NedwLUzIr72yQCdHYe2bCc19H3eyfsammiMur1P KtEAnik3lf96t2D1daJ4ZaiST8Rw5Qtd =0gqs -----END PGP SIGNATURE----- _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer This message has been scanned for viruses by MailControl - www.mailcontrol.com Click https://www.mailcontrol.com/sr/IIyLovGDSdTGX2PQPOmvUizKrmxxhcEGFn0HB2PmJETu!FF59CPCcZfM1iyAeuy4hu5YqLyvUFQhei1KLnaPDA== to report this email as spam. ________________________________ HR Wallingford and its subsidiaries uses faxes and emails for confidential and legally privileged business communications. They do not of themselves create legal commitments. Disclosure to parties other than addressees requires our specific consent. We are not liable for unauthorised disclosures nor reliance upon them. If you have received this message in error please advise us immediately and destroy all copies of it. HR Wallingford Limited Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom Registered in England No. 02562099 ________________________________ _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
