Hi Olivier Thanks for your suggestion - we discussed this at the PSC meeting on Monday night and Paolo Cavallini is going to be putting together a resource page for plugins developers and then putting out a call for them to start their plugin migration work.
Regards Tim > On 10 Jan 2018, at 10:34, Olivier Dalang <olivier.dal...@gmail.com> wrote: > > +1 for more stable release even if it's a few more weeks > > If feature freeze is confirmed, I would also suggest to send an email to all > plugin devs to say that no plugin will work anymore and to give some pointers > as to how to migrate the plugins to python/qgis 3. Most devs are probably > well aware of upcomming QGIS3, but this may still wake up some of us, and > centralizing the info about how to migrate to QGIS3 would be nice for all of > us anyway. > > Another email to both dev and uses mailing lists to encourage people to test > extensively with actual projects and to remind people on best practices to > report bugs (especially concerning whether a bug should be flagged as blocker > or not) would also probably be very useful to have better feedback from > testing. > > Thank you very much and happy new year :) > > Olivier > > > On Wed, Jan 10, 2018 at 8:45 PM, Tom Chadwin <tom.chad...@nnpa.org.uk > <mailto:tom.chad...@nnpa.org.uk>> wrote: > I know there is excitement, and I'm sure all the devs want the release done. > However, I think Juergen's proposal is the best (release 23 Feb): > > - more debugging time > - tallies with established release cycle > - respects the advice and plans of the Release Manager > > I 100% prioritise stability over early release. As you know, I'm not a QGIS > dev, so I'm speaking to you both as a user and as the manager of an > organization's installation base (about 30 seats). > > Yes, I know you will say we have LTR, but a significant aim of the QGIS > project is to increase our user base. As Nyall says, many people will hear > about the 3 release and try QGIS out. Stability is absolutely critical for > those first-timers. Their point of comparison is everyone's favourite > proprietary GIS. I imagine they also prioritise stability. > > Hope this makes sense > > Tom > > > > ----- > Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon > -- > Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html > <http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html> > _______________________________________________ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org <mailto:QGIS-Developer@lists.osgeo.org> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > <https://lists.osgeo.org/mailman/listinfo/qgis-developer> > _______________________________________________ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer — Tim Sutton Co-founder: Kartoza Project chair: QGIS.org Visit http://kartoza.com <http://kartoza.com/> to find out about open source: Desktop GIS programming services Geospatial web development GIS Training Consulting Services Skype: timlinux IRC: timlinux on #qgis at freenode.net
_______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
