[Qgis-developer] [Qgis-user] September 1 branch for release

[Marco Hugentobler]

 >are you saying that advertising the known issues is bad publicity or 
that releasing with open blockers is bad publicity

I wanted to say that advertising the known issues is bad publicity. 
Pointing to the bug tracker however is fine for me (it sounded to me as 
if the blockers would be listed next to the new features in the 
announcement).

Regards,
Marco



On 12.08.2013 16:10, Tim Sutton wrote:
> Hi
>
>
> On Mon, Aug 12, 2013 at 10:53 AM, Marco Hugentobler 
> <marco.hugentobler at sourcepole.ch 
> <mailto:marco.hugentobler at sourcepole.ch>> wrote:
>
>     Hi Tim
>
>     The proposed schedule sounds good to me.
>
>
>     >The proposal on the table is that any remaining blockers be
>     clearly listed as known issues in the release announcements.
>
>     Hm, don't you think this is bad publicity for the project? After
>     all, we don't list the other bugs as 'known issues', even though
>     they are known as well.
>
>
>
> Just to clarify Marco, are you saying that advertising the known 
> issues is bad publicity or that releasing with open blockers is bad 
> publicity? I think it is enough to point to the bug tracker and say 
> that there are still open issues for 2.0.
>
> Regards
>
> Tim
>
>
>     Regards,
>     Marco
>
>
>     On 12.08.2013 01:21, Tim Sutton wrote:
>>     Hi All
>>
>>     If we want to be ready with QGIS 2.0 for FOSS4G2013 we should
>>     ideally be ready to branch for release at the beginning of
>>     September (since most of us will be migrating to the land of deep
>>     fried mars bars for September).
>>
>>     Here is my proposal to achieve that:
>>
>>     * 12 Aug GUI Freeze, String Freeze, call for final translations
>>     * 25 Aug - Point of no return - final decision on whether to
>>     release with blockers
>>     * 1 Sept - Tag QGIS 2.0, call for packaging
>>     * 7 Sept - Public announcement of QGIS 2.0
>>
>>     Please consider the first item in the list in effect now, so the
>>     GUI and strings should not change except for critical bug fixes
>>     (icon tweaks and 'poodle fluffing the GUI' are no longer allowed).
>>
>>     Any remaining Blockers at point of release will be clearly
>>     identified as 'known issues'. On 25 August we (PSC) vote
>>     agreement on whether to go ahead with release or to postpone it.
>>     There would be an automatic revote each week until quorum is
>>     reached (basically giving us 2 postponement dates before FOSS4G).
>>     I really really really want QGIS 2.0 to be ready for FOSS4G and
>>     it would be nice to not be working on it at the QGIS HF in Brighton.
>>
>>     The proposal on the table is that any remaining blockers be
>>     clearly listed as known issues in the release announcements.
>>
>>     Speaking of release announcements, I have set up a very alpha-y
>>     web site for creating a visual changelog and I am looking for
>>     volunteers to add entries to this. If you have some time to write
>>     about the new features coming in QGIS 2.0 please contact me.
>>
>>     If those 'out there' in the community have the ability to fund
>>     the closing of the remaining blocker issues [1] either by
>>     donating money to QGIS or by sponsoring developer time
>>     independently of the QGIS project your contributions will be so
>>     gratefully received.
>>
>>     Finally a reminder that there is still a call out for nominations
>>     for new PSC members [2] so if you know someone suitable for the
>>     post, please go ahead and nominate them!
>>
>>     [1] http://hub.qgis.org/projects/quantum-gis/issues?query_id=23
>>     [2] http://hub.qgis.org/wiki/quantum-gis/PSC_Nominations_August_2013
>>
>>     Regards
>>
>>     Tim
>>
>>
>>     -- 
>>     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.
>>
>>     Irc: timlinux on #qgis at freenode.net <http://freenode.net>
>>     ==============================================
>>
>>
>>     _______________________________________________
>>     Qgis-user mailing list
>>     Qgis-user at lists.osgeo.org  <mailto:Qgis-user at lists.osgeo.org>
>>     http://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
>     -- 
>     Dr. Marco Hugentobler
>     Sourcepole -  Linux & Open Source Solutions
>     Weberstrasse 5, CH-8004 Zürich, Switzerland
>     marco.hugentobler at sourcepole.ch  <mailto:marco.hugentobler at sourcepole.ch>  http://www.sourcepole.ch
>     Technical Advisor QGIS Project Steering Committee
>
>
>     _______________________________________________
>     Qgis-developer mailing list
>     Qgis-developer at lists.osgeo.org <mailto:Qgis-developer at 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.
>
> Irc: timlinux on #qgis at freenode.net <http://freenode.net>
> ==============================================


-- 
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20130812/7132f5a8/attachment-0001.html>