Hi Martin On Sat, Oct 27, 2012 at 12:08 PM, Martin Dobias <[email protected]> wrote: > Hi Tim > > On Sat, Oct 27, 2012 at 1:41 AM, Tim Sutton <[email protected]> wrote: >> In terms of the release roadmap for 2.0 the following >> items were discussed in the hackfest in Essen as being the key >> features we would hold the release for: >> >> 1) Raster overhaul >> 2) WMTS Support >> 3) Atlas integration for composer >> 4) WCS Client support >> 5) Transactional WFS support for QGIS Server >> 6) SIP Bindings revision >> 7) Symbology overhaul (needs support for random colour assignment and >> property change on multiselections) >> 8) Sextante >> 9) Threading (non blocker wait fro 3.0) >> 10) Labelling overhaul >> 11) Diagrams overhaul (and remove of old implementation) >> 12) Oracle support (non blocker for 2.0) >> 13) Web site and docs update >> 14) Universal usage of expression builder >> >> We agreed that when these features are present we will roll out the >> release, with the hope that that could take place early next year. >> Come end of December I think we should take a look at the items listed >> and if any are obviously not making headway we should remove them from >> the blocker list or find out if there is a way to bring them to the >> foreground. The list above was also not intended to be exclusive, so >> if other developments are offered for incorporation they will be >> considered and accepted / declined on their merits. > > Thanks for the clarification. Even though I do not not fully > understand some items, it gives an idea of the plans. Would be good to > have a wiki page with few more details and status of the items: not > started / in progress / done. >
Thanks I will be moving the checklists from the wiki into the governance docs and will try to put more details there. > >> A last 'dreaming of a nicer vector api' note for Martin: Since you are >> adjusting the feature iterator API, wouldn't it also be nice to >> support this: >> >> for reading: >> >> while myProvider.nextFeature(myFeature): # or equivalent in new api >> myGeometry = myFeature.geometry() >> myFooValue = myFeature['foo'] >> .... do stuff ..... > > Good news, that's on the branch already ;-) Wohooo! Does that work for C++ api too? Regards Tim > > Cheers > Martin -- 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 [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
