Glad to hear you guys will meet on the 2.0 release. In the hope it can help your meeting, I'd like to share my 2 cents as a QGIS evangelist in Southeast Asia. Note, I'm running on QGIS master, so the argument below isn't out of self-interest ;o)
In the beginning of March 2013, Tim announced a proposed release schedule over the mailing list [1] which stated June 7, 2012 as date of release. Developers generally agreed around this schedule and process moved forward. In the meantime, QGIS end users and evangelists who keep track of development were left with a general sense of mid-2013 as QGIS 2.0 release, with all its glorious new features and fixes. When doing workshops, presentation on QGIS and discussing about it, "by end of June" was the best answer I - and surely many other QGIS evangelists praising QGIS out there - could give to people both excited about what's coming. But more importantly, this was a tentative dates when technical limitations and issues would be dealt with when planning forward. For e.g. in Southeast Asia, the broken state of Unicode shapefile encoding in QGIS 1.8 got many people to think twice about adoption. These issues were balanced out with an estimated date of delivery for 2.0 and plans have been drawn for QGIS adoptions in NGOs, ministries, public offices, etc. And this brings us to now. It seems inevitable that QGIS will have to be delayed. IMO, QGIS must insure the delay is as short as possible, to avoid negative impact on current end users expecting new features and issues fixed, as well as not being an obstacle to further adoption by missing an important deadline. Beyond the 80+ blockers currently listed, which could be dealt with in relatively short amount of time and focus, a SIP upgrade proposal is the other main "delayer". The argument for a delay to include the SIP upgrade is that, since the needed new vector API broke the plugins, and the SIP upgrade would also break plugins, the two should occur at the same time not to piss off plugin developers with too many breakages along the line. That's a valid argument, no question there, but shouldn’t be the only weighting factor, nor should it open the door to an absence of hard deadlines. I feel that for the SIP upgrade to be considered so late in the release process, it should be considered within _reasonable confines_ to avoid un-managed, harmful delays. Ideally, something along the lines of "merged by this coming Sunday or delayed to post 2.0". If the attempt at upgrading SIP is turning out to be more complex and take longer than a hard commit-to-master deadline, it IMO should be postponed on practical grounds of avoiding impact on QGIS end users and adoption. Alright, I don't claim having a perfect understanding of the bigger picture at play here, and I'm not intimately familiar with the source code, so disregard what's not proper. :) Still hope the above point of view, from a person trying to push for more QGIS adoption, can be of help. Regards Mathieu [1] http://lists.osgeo.org/pipermail/qgis-developer/2013-March/024685.html On Mon, Jun 3, 2013 at 4:24 AM, Tim Sutton <li...@linfiniti.com> wrote: > Hi > > Thanks very much Giovanni. We are holding a PSC meeting tomorrow to > plan the release strategy and your revisions will come in handy for > that. > > Regards > > Tim > > On Sun, Jun 2, 2013 at 11:30 AM, Giovanni Manghi > <giovanni.man...@faunalia.pt> wrote: > >> Giovanni could you do a triage of the blocker issue queue - it seems > >> like some could be removed (e.g. http://hub.qgis.org/issues/7619 > >> could be closed?). > > > > I checked the queue and cleaned it as much as possible. > > > > There is a small list of tickets that probably can be closed(*), but > > the other 71 are pretty much confirmed (almost all regressions). There > > is a bit of everything, big issues with edit tools, wfs client, ftools > > (many with memory leaks), printing, etc. > > > > > > (*) > > http://hub.qgis.org/issues/6383 > > > > http://hub.qgis.org/issues/6978 > > > > http://hub.qgis.org/issues/7458 > > > > http://hub.qgis.org/issues/7940 > > > > http://hub.qgis.org/issues/7668 > > _______________________________________________ > > Qgis-developer mailing list > > Qgis-developer@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > -- > Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > ============================================== > Please do not email me off-list with technical > support questions. Using the lists will gain > more exposure for your issues and the knowledge > surrounding your issue will be shared with all. > > Visit http://linfiniti.com to find out about: > * QGIS programming and support services > * Mapserver and PostGIS based hosting plans > * FOSS Consulting Services > Skype: timlinux > Irc: timlinux on #qgis at freenode.net > ============================================== > _______________________________________________ > 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
