Re: [warzone2100-dev] 1 hour left before the tagging of 2.3 B1 (also a comment about branches/2.2)
On 11/15/09, Zarel zarex...@x.com wrote: On Sat, Nov 14, 2009 at 12:10 PM, bugs buggy buginxx...@x.com wrote: About 1 hour left before I need to tag and build everything. This really is your last chance to get anything you wanted in 2.3B1. On Sat, Nov 14, 2009 at 2:53 PM, bugs buggy buginx...@x.com wrote: Warzone 2100 2.3 Beta 1 has now been released! But this isn't nearly as frustrating to me as the way you do it. Not nearly so bad this time, since the old version is still on the Download page since this is a beta. But usually, you just remove all other downloads from the download page, so for a short period of time, no one other than Windows users (and people who compile from source) can download Warzone. And for some reason, you see nothing wrong with this. Because there is nothing wrong with it? Seriously, when we do a new release, whatever the release is, then we want people to get the new release. The old versions go in the unsupported bin as far as I am concerned. We don't have the manpower to handle everything... Not even because I'm delaying the release, either. I usually get Mac builds up within 24 hours. It's been around 15 since tagging as of right now, and I have Mac builds up. That's shorter than the few days we're supposed to wait between tagging and announcing to release publicly. I've given up trying to convince you to leave old versions on the download page while the new versions haven't been built yet. But could you at least wait 24 hours for me? That's all I ask. I don't understand what the issue is time is short. I do as much as I can in the little amount of free time I have. I have no idea when or even if any other builds except the ones I make will (ever) be released. I have no clue if any of the other devs can or will do anything from the period I am off, to the period I get back. I don't know my schedule in advance, so that could be a few days or weeks or more. That is why, as soon as I finish the uploads, I throw them up, and have the Coming soon! tag for the missing versions. If I could make all builds I would, but unless Jobs sends me a mac, that isn't going to happen. When another dev can make the build they just edit the page... that isn't asking too much, and I am sure users understand that Coming soon! means just that... whenever someone has time to make it, they will. Time is the enemy here. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 1 hour left before the tagging of 2.3 B1 (also a comment about branches/2.2)
On 11/15/09, Dennis Schridde devurx...@xx.net wrote: A strict code-freeze for, say, a week, including the thorough testing on all OSes/arches as mentioned above, with the final builds being created right after the tag, might work just as well. Again, only provided that it is guaranteed that everything actually happens as planned and everyone starts working during that freeze already. Experience and this thing being a game, run in spare time, make me sceptic. But why not try something new, if you feel that suits you better. I (and thus the release-checklist) certainly do not want to stay in the way of advancement, but rather explain why some rules were invented. If there are better solutions to old problems, that is certainly a good thing. That would never work with the limited manpower time constraints many of us have. In a perfect world, with enough people to do everything on the release checklist, sure, but as it is now, that just is not possible and very impractical. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 1 hour left before the tagging of 2.3 B1 (also a comment about branches/2.2)
On Wed, Nov 18, 2009 at 2:53 PM, bugs buggy buginato...@gmail.com wrote: Because there is nothing wrong with it? Seriously, when we do a new release, whatever the release is, then we want people to get the new release. The old versions go in the unsupported bin as far as I am concerned. A Coming soon! message is not a new release. The old versions can't go in the unsupported bin before the new version is released. We don't have the manpower to handle everything... We have the manpower to release a new version before we remove the old version from the download page. I don't understand what the issue is time is short. I do as much as I can in the little amount of free time I have. I have no idea when or even if any other builds except the ones I make will (ever) be released. So? Let the rest of us handle it. I have no clue if any of the other devs can or will do anything from the period I am off, to the period I get back. I don't know my schedule in advance, so that could be a few days or weeks or more. That's no reason to handle a release so haphazardly. If you can't do a release well, just do the first half and let us clean up and do the release announcements, don't do it yourself poorly! That is why, as soon as I finish the uploads, I throw them up, and have the Coming soon! tag for the missing versions. If I could make all builds I would, but unless Jobs sends me a mac, that isn't going to happen. I told you, there are two superior options here: 1. Don't throw them up at all (and don't announce them). We can do that when we have the builds. 2. Leave the old version there, so people can download them. All I ask is that you do one of those (preferably the first). I believe we are in consensus that the first is the best option here. What is your objection to that? When another dev can make the build they just edit the page... that isn't asking too much, and I am sure users understand that Coming soon! means just that... whenever someone has time to make it, they will. There is no reason why a user should ever have to wait, if a version already exists. On the other hand, having coming soon appear on the Download page is a good way to turn away new users forever. If you find a new game online, but the download page just says Coming soon!, you're going to leave and probably forget about it. But that really distracts from the main point, which is that there's NO REASON why the user should see that message in the first place, instead of a download for the game they came to download. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.3 Beta 2 release ETA 11-21-09
Hello! Am Mittwoch, 18. November 2009 22:18:40 schrieb bugs buggy: All known fixable *REPORTED* bugs for 2.3b1 have been squashed, so we need another beta release to keep our testing pool testing. :) The plan is to have another release this Saturday, the 21st. In response to the recent discussion, I'd add that now everyone with time and interest could try to build and test $svn/branches/2.3 (assuming there are no changes about to happen on it anymore), so that the release builds can be created quickly after the tag. --devurandom signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev