Re: [Qgis-user] [Qgis-developer] Realease and blockers
Hello all, Not sure if this is how it works, but can we propose that the ?small? donations gathered by the Portuguese Users Group (570€) be directed for this bugfixing? Thanks, Alexandre Neto On Fri, Jun 6, 2014 at 12:57 PM, Matthias Kuhn wrote: > While testing and reporting is important without a doubt, the currently > outstanding issues could be fixed easily by the end of the month as soon > as resources are available. > > The main point is, that we should start improving where there is the > biggest effect - and that's paid bugfixing time. There are some > extremely capable and effective core devs available for this job as has > been proven in the past. > > That means: go out, tell your neighbours and social media buddies and > customers about the RC and testing. But if you want the bugs they report > to be fixed, make sure that there's somebody taking care of them. The > main problems normally are not the bugs not found while testing, but the > ones not fixed before the release. This in turn also means that I don't > think a two months bugfixing period will improve a lot. If there's two > months with developers spending time on other projects because there's > no funding available for bugfixing we haven't won anything. > > Regards, > Matthias > ___ > Qgis-developer mailing list > qgis-develo...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
I have just written a blog post and added it to Twitter, Google+, Facebook. I have also updated the banners on all those sites to show the RC banner. Blog post is at http://nathanw.net/2014/06/06/help-qgis/ - Nathan On Fri, Jun 6, 2014 at 10:27 PM, Anita Graser wrote: > On Fri, Jun 6, 2014 at 1:34 PM, Alexander Bruy > wrote: > > 2014-06-06 13:16 GMT+03:00 Vincent Picavet : > >> Could we make a more visible RC release on the website, encouraging > testing ? > >> > >> I think that our user are not used yet to our new release cycle. We > really > >> should educate them, and lower the barrier to RC testing and bug > reporting. As > >> for now, even installing the RCs is complicated, so is bug reporting. > > > > We already have a big banner at main page about RC and testing. Seems > most > > users don't visit main page too often to notice it. > > We've also advertised the release candidates quite heavily on Twitter. > I don't think there is much chance to reach those users which we > haven't reached so far. > > Best wishes, > Anita > > > > > > > ___ > > Qgis-developer mailing list > > qgis-develo...@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ > Qgis-developer mailing list > qgis-develo...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
On Fri, Jun 6, 2014 at 1:34 PM, Alexander Bruy wrote: > 2014-06-06 13:16 GMT+03:00 Vincent Picavet : >> Could we make a more visible RC release on the website, encouraging testing ? >> >> I think that our user are not used yet to our new release cycle. We really >> should educate them, and lower the barrier to RC testing and bug reporting. >> As >> for now, even installing the RCs is complicated, so is bug reporting. > > We already have a big banner at main page about RC and testing. Seems most > users don't visit main page too often to notice it. We've also advertised the release candidates quite heavily on Twitter. I don't think there is much chance to reach those users which we haven't reached so far. Best wishes, Anita > ___ > Qgis-developer mailing list > qgis-develo...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
Hi, Le vendredi 6 juin 2014 13:34:12, Alexander Bruy a écrit : > 2014-06-06 13:16 GMT+03:00 Vincent Picavet : > > Could we make a more visible RC release on the website, encouraging > > testing ? > > > > I think that our user are not used yet to our new release cycle. We > > really should educate them, and lower the barrier to RC testing and bug > > reporting. As for now, even installing the RCs is complicated, so is bug > > reporting. > > We already have a big banner at main page about RC and testing. Seems most > users don't visit main page too often to notice it. I tried with a "standard" user yesterday, watching him use the site to get qgis, and it was still _very_ complicated for him. He expected to click on a "QGIS 2.4 preview download" button and the download to begin immediatly, which is far from happening. Instead, the small RC link leads to a page with a lot of links, he had difficulties to find the preview release (not knowing what a "release candidate" is), hesitating with osgeo4w download, then being redirected once again on the same page, lost in the web page, finally finding a small link to a dull page listing a lot of files (what the hell is a md5sum file ?? what is this 2.3 version ?? where is the preview ?), of which he finally chose a random exe and installed it. Even I was totally lost trying to get the right file. I think we can do much better. Then it is a matter of advertising the preview at large : official "call for testing" from qgis project on osgeo mailing lists, twitter, linkedin, and if possible on a qgis-news mailing list where we have gathered a lot of user beforehand (with their approval of course). Vincent ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
On 06/06/2014 8:51 pm, "Vincent Picavet" wrote: > > More bug reports, bug comments and better bug reports is already a lot of > developer's time saved. > Having more testers (and regular testers) is as important as having developers > to fix bugs. Sorry if I didn't word my original reply very well - I didn't mean to imply bug reports aren't important or valued! I'm just unsure how we can clear our current queue in time for release as it stands currently... Nyall ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
2014-06-06 13:16 GMT+03:00 Vincent Picavet : > Could we make a more visible RC release on the website, encouraging testing ? > > I think that our user are not used yet to our new release cycle. We really > should educate them, and lower the barrier to RC testing and bug reporting. As > for now, even installing the RCs is complicated, so is bug reporting. We already have a big banner at main page about RC and testing. Seems most users don't visit main page too often to notice it. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
Hello, Le vendredi 6 juin 2014 12:30:23, Nyall Dawson a écrit : > On 06/06/2014 8:20 pm, "Vincent Picavet" wrote: > > Could we make a more visible RC release on the website, encouraging > testing ? > > > I think that our user are not used yet to our new release cycle. We > > really should educate them, and lower the barrier to RC testing and bug > reporting. As for now, even installing the RCs is complicated, so is bug > reporting. > > I don't think the issue is just bug reporting for a RC though. As > mentioned, we've already got a very long blocker list, which is still > growing. > I think a bigger issue is development resources and developer's time > availability. At the current rate of bug closing we're very likely to still > have a large number of these issues outstanding at the end of the month. More bug reports, bug comments and better bug reports is already a lot of developer's time saved. Having more testers (and regular testers) is as important as having developers to fix bugs. My proposal was also more oriented towards getting users involved in all ways, and especially funding at Feature Freeze time. Getting them to download, install and test more thoroughly the RCs, and using this media to incent them to fund the software do contribute to more developers time. > I'm in favor of a longer freeze period for next release. I am not sure that more non-paid developer time is a sustainable model. Or it is a matter of going from a FF development model, to a more formal peer- review commitfest model ( like http://rhaas.blogspot.fr/2011/03/commitfests- and-meritocracy.html ). There are many other ways to reduce bugs even before reaching feature freeze, some of them already discussed thoroughly here, I am just trying to find some easy, reachable and efficient means, which can of course be complementary to other means. Vincent ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
On 06/06/2014 8:20 pm, "Vincent Picavet" wrote: > > Could we make a more visible RC release on the website, encouraging testing ? > > I think that our user are not used yet to our new release cycle. We really > should educate them, and lower the barrier to RC testing and bug reporting. As > for now, even installing the RCs is complicated, so is bug reporting. > I don't think the issue is just bug reporting for a RC though. As mentioned, we've already got a very long blocker list, which is still growing. I think a bigger issue is development resources and developer's time availability. At the current rate of bug closing we're very likely to still have a large number of these issues outstanding at the end of the month. I'm in favor of a longer freeze period for next release. Nyall ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] [Qgis-developer] Realease and blockers
Hello, Le vendredi 6 juin 2014 11:08:57, Paolo Cavallini a écrit : > The new QGIS version will be released very soon. There are still 58 > blocking issues, growing. Some of them are quite nasty. I urge everybody, > and especially those who use QGIS in large organization, saving tons of > money previously spent in licences, to quickly invest a fraction of these > savings into fixing some of these. With >1 million users, this seems a > feasible target. Could we make a more visible RC release on the website, encouraging testing ? I think that our user are not used yet to our new release cycle. We really should educate them, and lower the barrier to RC testing and bug reporting. As for now, even installing the RCs is complicated, so is bug reporting. What about modifying the RCs so that : * we have a bug report feature in the help menu, allowing to create an osgeo user, search for bug and report if not found ? * we add a splash-screen or a first pop-up window stating clearly that there is a need for bugfixes, and therefore a strong and quick need for funding ? Maybe even adding links to supporting companies as stated on the website, so that users/clients can contact them directly, in addition to the sponsoring informations ? * we add to this popup a big "donate now" button linking to paypal / flattr or whatever simple system for micro-donation, and a bitcoin address * we propose to optionnally subscribe to a specific qgis-newsletter mailing list, where we can reach our userbase with RC download links, and funding requests (with a privacy protection + no spam statement) This is a bit late for 2.4 of course, but this is IMHO a way to enlarge our tester base, as well as our funders. What we need is not a different release cycle, but more education. Adopting more push-oriented communication methods seams the way to go. My 2 cents, Vincent ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
