<div dir="ltr">Hi<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 12, 2013 at 4:15 PM, Marco Hugentobler <span dir="ltr"><<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div><div class="im">>are you saying that advertising the
known issues is bad publicity or that releasing with open blockers
is bad publicity<br>
<br></div>
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).<br>
<br></div></div></blockquote><div><br></div><div>Ok great and agreed - thanks for the clarification!</div><div><br></div><div>Regards</div><div><br></div><div>Tim</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div>
Regards,<br>
Marco<div><div class="h5"><br>
<br>
<br>
<br>
On 12.08.2013 16:10, Tim Sutton wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">Hi
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Aug 12, 2013 at 10:53 AM,
Marco Hugentobler <span dir="ltr"><<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi Tim<br>
<br>
The proposed schedule sounds good to me.
<div><br>
<br>
>The proposal on the table is that any remaining
blockers be clearly listed as known issues in the
release announcements.<br>
<br>
</div>
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.<br>
<br>
<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Tim</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div> <br>
Regards,<br>
Marco
<div>
<div><br>
<br>
On 12.08.2013 01:21, Tim Sutton wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">Hi All
<div><br>
</div>
<div>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).</div>
<div><br>
</div>
<div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">Here
is my proposal to achieve that:</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br>
</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">
* 12 Aug GUI Freeze, String Freeze, call for
final translations</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">*
25 Aug - Point of no return - final decision
on whether to release with blockers</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">*
1 Sept - Tag QGIS 2.0, call for packaging</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">*
7 Sept - Public announcement of QGIS 2.0</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br>
</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">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).</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br>
</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">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.</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br>
</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">The
proposal on the table is that any remaining
blockers be clearly listed as known issues
in the release announcements.</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br>
</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px">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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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!</div>
<div><br>
</div>
<div>[1] <a href="http://hub.qgis.org/projects/quantum-gis/issues?query_id=23" target="_blank">http://hub.qgis.org/projects/quantum-gis/issues?query_id=23</a><br>
</div>
<div>[2] <a href="http://hub.qgis.org/wiki/quantum-gis/PSC_Nominations_August_2013" target="_blank">http://hub.qgis.org/wiki/quantum-gis/PSC_Nominations_August_2013</a></div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Tim</div>
<div><br>
</div>
<div><br>
</div>
-- <br>
<div dir="ltr">Tim Sutton - QGIS Project
Steering Committee Member (Release Manager)<br>
==============================================<br>
Please do not email me off-list with
technical<br>
support questions. Using the lists will gain<br>
more exposure for your issues and the
knowledge<br>
surrounding your issue will be shared with
all.<br>
<br>
Irc: timlinux on #qgis at <a href="http://freenode.net" target="_blank">freenode.net</a><br>
==============================================</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<div>
<pre>_______________________________________________
Qgis-user mailing list
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a>
</pre>
</div>
</blockquote>
<span><font color="#888888"> <br>
<br>
<pre cols="72">--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a> <a href="http://www.sourcepole.ch" target="_blank">http://www.sourcepole.ch</a>
Technical Advisor QGIS Project Steering Committee </pre>
</font></span></div>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Tim Sutton - QGIS Project Steering Committee
Member (Release Manager)<br>
==============================================<br>
Please do not email me off-list with technical<br>
support questions. Using the lists will gain<br>
more exposure for your issues and the knowledge<br>
surrounding your issue will be shared with all.<br>
<br>
Irc: timlinux on #qgis at <a href="http://freenode.net" target="_blank">freenode.net</a><br>
==============================================</div>
</div>
</div>
</blockquote>
<br>
<br>
<pre cols="72">--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a> <a href="http://www.sourcepole.ch" target="_blank">http://www.sourcepole.ch</a>
Technical Advisor QGIS Project Steering Committee </pre>
</div></div></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Tim Sutton - QGIS Project Steering Committee Member (Release Manager)<br>==============================================<br>Please do not email me off-list with technical<br>
support questions. Using the lists will gain<br>more exposure for your issues and the knowledge<br>surrounding your issue will be shared with all.<br><br>Irc: timlinux on #qgis at <a href="http://freenode.net" target="_blank">freenode.net</a><br>
==============================================</div>
</div></div>