[Qgis-psc] Vote about release plan

[Nathan Woodrow]

Going for 3.0 also about when and why we break API with more of a lean
towards the why.  For me the only thing really forcing us is PyQt5 and that
is the only real driver, pretty much everything else can be retro fitted
in.  Not nice but breaking API just just because and for a version number
isn't cool.

So with that said when are we going to be forced to go to PyQt5? If we
aren't going to be forced for a while then I think we should just keep
keeping on and do 3.0 later.

If I had a vote it would be to stay with 2.x for as long as we can until
forced with PyQt5, we can always write wrappers over hard to us APIs

Nathan

On Fri, 17 Apr 2015 12:24 am Marco Hugentobler <
marco.hugentobler at sourcepole.ch> wrote:

> Hi
>
>  From the last psc meeting and the following discussion on the mailing
> list (http://lists.osgeo.org/pipermail/qgis-psc/2015-April/002966.html
> and following mails) it seems most people are happy with skipping the
> 2.10 release and having 3.0 in autumn (feature freeze September, release
> october).
>
> It will be good to have an official PSC decision with voting about it.
> Please give your votes if you agree with skipping 2.10 and go for 3.0 in
> autumn.
>
> (obviously +1 for me).
>
> Regards,
> Marco
>
> --
> Dr. Marco Hugentobler
> Sourcepole -  Linux & Open Source Solutions
> Weberstrasse 5, CH-8004 Zürich, Switzerland
> marco.hugentobler at sourcepole.ch http://www.sourcepole.ch
> Technical Advisor QGIS Project Steering Committee
>
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-psc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20150416/7b6af56a/attachment.html>