Hi ! Just for information : - will QGis 2.0 have the PyQt API changed to version 2 ? - will it have a separate plugin folder than QGis 1.8 ?
Thanks ! Olivier 2013/3/15 Tim Sutton <li...@linfiniti.com> > Hi All > > Just to confirm on this thread that following the discussions here the > following updated timeline to 2.0 will apply: > > 1 April 2013 - Feature freeze - no new features in master > 1 May 2013 - GUI Freeze and String freeze - no changes to ui or > strings except where required for critical bug fixes. Call for > translations. > 1 June 2013 - Branch 2.0, code freeze (except for packaging related > changes), call for packaging > 7 June 2013 - Public release of 2.0 > > Regards > > Tim > > On Fri, Mar 15, 2013 at 5:44 PM, Marco Hugentobler > <marco.hugentob...@sourcepole.ch> wrote: > > Pushed to master branch now. > > > > > > On 13.03.2013 17:44, Marco Hugentobler wrote: > >> > >> Hi devs > >> > >> The first part of the symbology improvements is available in my github > >> fork: > >> > >> https://github.com/mhugent/Quantum-GIS/tree/data_defined_symbology > >> > >> Currently, one symbol is either in mm or in map units. The changeset in > >> the branch adds the possibility to mix different output units ( mm / map > >> units ) in one symbol and even in one symbol layer. So it is now e.g. > >> possible to have line width in mm and line offset in map units. > >> > >> Let me know if you have feedback on this. Next enhancement part will be > to > >> add more data defined symbol properties (from attribute / expression). > >> > >> Regards, > >> Marco > >> > >> On 04.03.2013 13:07, Marco Hugentobler wrote: > >>>> > >>>> Moving the date to say start of April wouldn't > >>>> hurt. Would that help? > >>> > >>> > >>> Start of April would be ok for the data defined symbology. > >>> > >>> Regards, > >>> Marco > >>> > >>> On 04.03.2013 11:44, Jürgen E. Fischer wrote: > >>>> > >>>> Hi Marco, > >>>> > >>>> On Mon, 04. Mar 2013 at 11:37:15 +0100, Marco Hugentobler wrote: > >>>>> > >>>>> Disadvantage is that 15 March is too close for it to go into master. > >>>>> What > >>>>> should we do (wait for 2.1 / shift feature freeze date / exception > >>>>> from > >>>>> feature freeze) ? > >>>> > >>>> How much time would you need? Moving the date to say start of April > >>>> wouldn't > >>>> hurt. Would that help? > >>>> > >>>> Jürgen > >>>> > >>> > >>> > >> > >> > > > > > > -- > > Dr. Marco Hugentobler > > Sourcepole - Linux & Open Source Solutions > > Weberstrasse 5, CH-8004 Zürich, Switzerland > > marco.hugentob...@sourcepole.ch http://www.sourcepole.ch > > Technical Advisor QGIS Project Steering Committee > > > > _______________________________________________ > > 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