<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">I am aware it was a late email, I have been busy on non qgis jobs and haven't been able to look side ways.</div><div class="gmail_quote"><br></div><div class="gmail_quote">
On Fri, Jun 27, 2014 at 2:03 AM, Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div id=":44f" class="" style="overflow:hidden">1. do not change anything in the relase schedule just one day before<br>
2. announcements should be clear: (a) QGIS 2.4 is out, wait for packages; (b) package<br>
for {Debian|Ubuntu|whatever} is ready, go and download it from http://...<br></div></blockquote></div><br>1. Surly it's not hard to build the package an two hours or so before the release and have it ready go, even if this a last minute call. As much as it pains people Windows is our biggest user base so they need to be there, followed by Debian, then OS X. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">2) There is no different for a user between a) and b) a "release" is a binary release like I said. Making it a two stage process is just confusing and annoying to users. Trying to make people understand the "process" by doing this isn't really right IMO. Users don't need to care how packages are built or how long it takes, the people that know or need too tend to be involved at the project level anyway. Users just need a package to install on release day, a "source" release is like say "yay release!....But no you can't have it because your just a user you have to wait".</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">Jürgen, </span><br></div><div class="gmail_extra"><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px"><br>
</span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">Looks like announcing the (source) release on qgis-developer and announcing<br>
</span><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">individual packages on qgis-user would solve that problem.</span></blockquote><div class="gmail_extra"><br></div><div class="gmail_extra">
This will make no difference, people watch the dev list especially around release time for news. Once you announce any kind of "release", source or not, you have lost the ability to control where it will go and what people expect. Just watch how quick it will hit twitter, and then watch as people get confused why there is no download. It's mainly wording, it's all in the wording.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">People really like our software and some are super excited about the release, to not have packages for download really looks bad IMO.</div><div class="gmail_extra">
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">To me there's not much point in having master frozen, while everyone is just<br>
</span><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">waiting for packages to be built.</span></blockquote><div><br></div><div>That is why I said it would only be a day or so before release, it shouldn't take more then day to build a package for any of the major platforms and update the site. All we would have to do is branch the code a day out, package, release. If you push something non package related on that last day before the release then it will just have to wait until next release, or a patched release. People can't be pushing fixes last second as that is just dangerous.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">That was the first time - it might have come unexpected to the user. They'll<br>
</span><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">probably get used to it.</span>. </blockquote><div><br></div><div>They shouldn't that is the point I'm making. We don't expect that with other things. If I see a new release of Python is out and I go to the site and don't see a binary package it will be a long while before I go back I have other things to be doing.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">I rather get the (source) release done, get my packages done (a good share of<br>
</span><span style="color:rgb(0,0,0);font-family:arial,sans-serif;font-size:13px">the above) and then get back to master...</span></blockquote><div><br></div><div>I understand, just don't call it a "release". Branch it today and call it a "call for packages" (don't use the word "out" or "release"), wait a few days then binary release. You and I know what a source release is, users don't care. We really need some stats on our user base so we know what platforms are our major target ones.</div>
<div><br></div><div>This raises the question how quickly are you expecting to have major packages done? If we source release tonight but don't have packages ready by Monday, Tuesday, there is 4 days of people hitting our site with no way to download the packages and this looks really bad.</div>
<div><br></div><div>Why not call for packages today, let people get sorted over the weekend, update the site, release on Monday, Tuesday? </div><div><br></div><div>I know it sounds like a rant, because it kind of is, but I really enjoy working on the project, the package is great, the people are great, but I find this current release process stressful and I'm not one calling the release. Stressful because I know we have a lot of users who love our stuff but can't get it when we say it's "out".</div>
<div><br></div><div>If you don't want to change it for this release, OK, but I think we need to review it for the next release so everyone is on the same page. There are are other large projects we can steal the process from.</div>
<div><br></div><div>- Nathan</div></div>