How about making a formal announcement (mailing list, website, wiki etc) telling the users that QGIS version 2.X is in feature freeze and therefore is sufficiently stable to be tested by end users? This may increase the number of testers.
As an end user that uses QGIS for production, this is the only time I work with QGIS Master. On Mon, Feb 24, 2014 at 2:17 PM, Jonathan Moules < jonathanmou...@warwickshire.gov.uk> wrote: > > >> Why not? We're talking about a feature freezed period!? The nightly >> build >> is a snapshot what what will get release. Where do you see a difference? >> > > I think it's a perception thing. > "Nightly build" in my mind always means "bleeding edge may or may not > work, use at own risk." I'm aware that doesn't always mean "*it will > crash your computer, burn down your house, and spend your life savings on > questionable drugs*", but it's certainly not what I see as a synonym for > "stable" either. > > Every time I see a nightly, it always comes with a big scary caveat (QGIS > does too - http://www.qgis.org/en/site/forusers/alldownloads.html ). This > trains users not to use them. Taking one of the nightlies and re-branding > it to something more amicable would get more folks to test it. Just copy > and paste it and rename the file. :-) > > Cheers, > Jonathan > > >> >> >> > Very few average user will install a nightly development build, but you >> get >> > an higher chance of getting a broader number of people (that interacts >> with >> > QGIS in different ways) to test out your product before it's released. >> >> Why should it matter if we call it "weekly snapshot", "nightly build" or >> "prerelease"? It's the same thing, just the tag is different. And >> installation is essential as easy as installing the stable release. >> >> >> > It also helps channel what your describing as noise (i.e. users running >> > into problems) into a better managed call for people to test and report. >> > The noise will happen no matter what. But it might make some sense to >> > trigger some of that noise (valid bugs and "invalid" RTFM cases) >> _before_ >> > you release your final version via a pre-release social media and news >> site >> > "try this pre-release build" :) >> >> > It's really more a matter of presentation to the users than of actual >> work. >> >> Exactly. And that's what I meant with noise: "tada, there's a new weekly >> snapshot/prerelease/nightly build" - not users running into problems. >> Because >> I see that as the only significant difference to what we already 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 >> 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 >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> > > > This transmission is intended for the named addressee(s) only and may > contain sensitive or protectively marked material up to RESTRICTED and > should be handled accordingly. Unless you are the named addressee (or > authorised to receive it for the addressee) you may not copy or use it, or > disclose it to anyone else. If you have received this transmission in error > please notify the sender immediately. All email traffic sent to or from us, > including without limitation all GCSX traffic, may be subject to recording > and/or monitoring in accordance with relevant legislation. > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
