[Qgis-developer] -10 countdown to QGIS 2

[Nathan Woodrow]

As much as it would be nice to have all this bugs marked against 2.0 fixed
before release I can't see that happening.  We have already delayed this
release by a long time as is. Most of the concern now should be on the
blocking list, which it has been over the last couple of weeks. We are also
already in string freeze so we can't go doing anything major in terms of UI
changes that might stuff up the translation process.

This is not saying that other bugs can't be fixed but we need to cut the
line and release once the blockers are done or else we are never going to
get it out. People, developers included, are just going to get frustrated
by the delays. If we draw the line and release it will always just be a
game of "just wait for this next bit; and this next bit; and this next
bit".  It's not like 2.0 is going to be the final release we ever make.

I think is Tim's plan is releasing on/before FOSS4G, which would be really
good for me. I would really like to draw up hype with my QGIS 2.0 keynote
and having it released would be a good start. Tim is planning to revamp and
style the new website this week which will be nice. Apart from fixing the
blockers and revamping the site I can't see anything stopping a release.
 The manual is a on going effort, even after the release, and because now
it's all rst and html output it will be easier to keep people up to date.

- Nathan


On Mon, Jul 22, 2013 at 11:06 PM, rldhont <rldhont at gmail.com> wrote:

> Le 22/07/2013 15:04, Paolo Cavallini a écrit :
>
>  -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Il 22/07/2013 14:59, rldhont ha scritto:
>>
>>> HI all,
>>>
>>> Thanks to Salvatore Larosa which points that we are at 10 blockers
>>> before QGIS 2.
>>>
>>> But I take a look at the bug trackers :
>>> * 10 issues are blockers bugs
>>>    * 6 target the version 2.0
>>> * 43 issues have high priority
>>>    * 31 are bugs
>>>    * 25 target the version 2.0
>>> * 1036 issues have normal priority
>>>    * 402 target the version 2.0
>>>    * 365 are bugs and target the version 2.0
>>>
>> Please note that, although on a separate Redmine instance, sextante
>> issues also add
>> to the figure. Ideally they should be migrated to qgis desktop instance,
>> but this
>> will imply missing the subcategory classification, which IMHO is not good.
>>
>>  I would like to know, as a contributor, what we have to do before QGIS
>>> 2.0 ?
>>>
>> Besides going and fix issues yourself, I think the most effective
>> approach so far has
>> been directly sponsoring one developer to go full time bugfixing.
>> If we get significant new donations, we can keep on supporting this
>> approach.
>> BTW, Juergen is doing a wonderful job - thanks him, Andreas for starting
>> this, and
>> all the sponsors and donors to make it possible.
>>
>
> How can I find all the bugs the community want to fixe before QGIS 2 ?
>
>
>
>> All the best.
>> - -- Paolo Cavallini - Faunalia
>> www.faunalia.eu
>> Full contact details at www.faunalia.eu/pc
>> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/**calendario<http://www.faunalia.it/calendario>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.12 (GNU/Linux)
>> Comment: Using GnuPG with Icedove - http://www.enigmail.net/
>>
>> iEYEARECAAYFAlHtLfQACgkQ/**NedwLUzIr5ccwCdGfdQIJ0kwa2ObS9**+d1ESg9Hq
>> iQcAoIy5HnoQM12nKps+**e9T44rUCogpY
>> =0LDI
>> -----END PGP SIGNATURE-----
>> ______________________________**_________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/**mailman/listinfo/qgis-**developer<http://lists.osgeo.org/mailman/listinfo/qgis-developer>
>>
>
> ______________________________**_________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/qgis-**developer<http://lists.osgeo.org/mailman/listinfo/qgis-developer>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20130722/4df322a7/attachment.html>