<div dir="ltr">>><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">No. Just like with 2.2.</span><div><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px"><br></span></div>
<div><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">I think this is a real mistake and bad PR for the project. If we want to do it like this we need to refine out release plan better to have things line up nice and smooth so people get what they expect. The user isn't us, we can build from source, they can not, nor should they.</span></div>
<div><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font color="#000000" face="arial, sans-serif">dev cylce -> freeze -> no new strings -> 3 days out (or something) freeze all non package code incl strings -> call packages/update versions/update site code etc -> (on day) push website and packages -> announcement.</font></div>
<div><font color="#000000" face="arial, sans-serif"><br></font></div><div><font color="#000000" face="arial, sans-serif">I suggest we need a calender on the website that shows using colors and date ranges what is happening and when so no one gets a shock. </font></div>
<div><font color="#000000" face="arial, sans-serif"><br></font></div><div><font color="#000000" face="arial, sans-serif">Here is what the current release feels like to a normal user who is coming from the outside:</font></div>
<div><font color="#000000" face="arial, sans-serif"><br></font></div><div><font color="#000000" face="arial, sans-serif">- Gets notified of the release (took about 10 seconds to go on twitter after you sent the 2.2 email that it was "out" so it was not a hidden thing, even on the weekend)</font></div>
<div><font color="#000000" face="arial, sans-serif">- Gets excited</font></div><div><font color="#000000" face="arial, sans-serif">- Heads to website</font></div><div><font color="#000000" face="arial, sans-serif">- "Ok banner still say 2.2 but there is a download link"</font></div>
<div><span style="color:rgb(0,0,0);font-family:arial,sans-serif">- Click download.</span></div><div><span style="color:rgb(0,0,0);font-family:arial,sans-serif">- Run installer</span></div><div><span style="color:rgb(0,0,0);font-family:arial,sans-serif">- "oh 2.2. Didn't it say 2.4 was out?"</span></div>
<div><span style="color:rgb(0,0,0);font-family:arial,sans-serif">- *check back for later for you packages* "How long do I have to wait?"</span></div><div><span style="color:rgb(0,0,0);font-family:arial,sans-serif">- *........ please come again*</span></div>
<div>- (Never comes back) or is annoyed as heck</div><div>- *meanwhile*</div><div>- We push master forward, features flow in like normal.</div><div>- "Oh hi I found a major bug in 2.4 is there any planned patched release"</div>
<div>- "Meh" </div><div><br></div><div>This is bad PR, even without the patched release thing, a release is a binary release to a user. A source tarball means nothing.</div><div><br></div><div>I remember having to respond to a heap of annoyed people on the QGIS twitter/Facebook account with "we are currently building package, please hold"</div>
<div><br></div><div>- Nathan</div><div><font color="#000000" face="arial, sans-serif"><br></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 26, 2014 at 9:58 PM, Jürgen E. <span dir="ltr"><<a href="mailto:jef@norbit.de" target="_blank">jef@norbit.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nathan,<br>
<div class=""><br>
On Thu, 26. Jun 2014 at 21:22:54 +1000, Nathan Woodrow wrote:<br>
> 1) Are we planning on having packages ready to go before the official<br>
> announcement?<br>
<br>
</div>No. Just like with 2.2.<br>
<div class=""><br>
<br>
> 2) Is the website going to be updated before/just after the announcement to<br>
> point to the packages?<br>
<br>
</div>When the package arrive the website is going to be updated. Where necessary,<br>
not all links have an explicit version number in them. And we should probably<br>
also get rid of those that do - so we don't need to change that just because<br>
the current release version number changed.<br>
<div class=""><br>
<br>
> 3) Are we holding the feature freeze for a month/two weeks after release in<br>
> case something comes up that is a real hurt point to hold off on?<br>
<br>
</div>No. Once the release is branched and tagged, master is open for new features<br>
again. Just like with 2.2. Fixes can be applied to the release branch -<br>
although there still isn't an official plan if/when/how such updates would end<br>
up in packages.<br>
<div class=""><br>
<br>
> If 2.4 "release" on the 27 is going to be just a email to call for packages,<br>
> could it be just labeled as such, don't use the words "Release", or "QGIS 2.4<br>
> is out" because it will go everywhere raising the issues in 1).<br>
<br>
</div>No, just like with 2.2<br>
<br>
<a href="http://lists.osgeo.org/pipermail/qgis-user/2014-February/026281.html" target="_blank">http://lists.osgeo.org/pipermail/qgis-user/2014-February/026281.html</a><br>
<br>
and as on the roadmap:<br>
<br>
<a href="http://qgis.org/en/site/getinvolved/development/index.html#road-map" target="_blank">http://qgis.org/en/site/getinvolved/development/index.html#road-map</a><br>
<br>
<br>
Jürgen<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br>
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50<br>
Software Engineer D-26506 Norden <a href="http://www.norbit.de" target="_blank">http://www.norbit.de</a><br>
QGIS PSC member (RM) Germany IRC: jef on FreeNode<br>
<br>
--<br>
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH<br>
Rheinstrasse 13, 26506 Norden<br>
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502<br>
</font></span><div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br></div>