Re: [Warzone-dev] Version numbering
On 9/25/08, Zarel [EMAIL PROTECTED] wrote: 2008/9/24 bugs buggy [EMAIL PROTECTED]: We got windows builds available nightly. We should use that to our advantage, and let the community test. I don't know how we will handle mac builds though. It doesn't look like we will have nightly builds with them. But 2 out of the 3 platforms we support isn't all that bad, it should at least find most of the errors that way. Well, I suppose I can make Mac builds every week or so. Will that be close enough? -Zarel Weekly is fine, however, you need to know how to modify the xcdoe stuff to add libs, and stuff like that. It was suggested on the forums that macs could use macports, but I guess that is frowned on. It would be nice to simplify the build process to maintain, since currently, it seems to be above most everyone's skill level to maintain the xcode stuff in its current form. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Version numbering
Dennis Schridde schreef: I'd like to hear your opinions, ideas, insights. Maybe you've got a different/better idea how to prevent long times of silence between releases? Quick short: I'd rather release early and often (with some bugs) than less often with less frequent testing. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Version numbering
2008/9/24 bugs buggy [EMAIL PROTECTED]: We got windows builds available nightly. We should use that to our advantage, and let the community test. I don't know how we will handle mac builds though. It doesn't look like we will have nightly builds with them. But 2 out of the 3 platforms we support isn't all that bad, it should at least find most of the errors that way. Well, I suppose I can make Mac builds every week or so. Will that be close enough? -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[Warzone-dev] Version numbering
Hello everyone. As we are in discussion mood already, what do you think about making bugfix releases? Is that something we should continue? Should we instead invest a bit more time into QA before each feature release (gather some testers from the community maybe?) and then stop caring about a release branch after we released the final version? Instead of releasing betas before the release, making the .0 release and then pushing bugfixes afterwards, we would only push alphas and betas (just a difference in name, to distinct the grades of stability) and a final release, but those prereleases would be more and come more often. After the final release we could fully concentrate on trunk and new features again. On the other hand doing bugfix releases we are able to fix smaller issues after a release via backports, and also by investing time into the diverged codebases of branches/* and trunk. It is mainly the choice between (rock?) stable x.y.z releases with more time to the next feature-release, or earlier feature releases with probably a few more bugs during the lifetime of the product. The later could be compensated if we'd find more of the bugs earlier, by having good testing (i.e.). Two-weekly prereleases, no matter of the current state, sounds like a good plan, with alphas starting right when the major features are merged. This is an idea to prevent those long times between releases as we had them for the 2.1 series. I'd like to hear your opinions, ideas, insights. Maybe you've got a different/better idea how to prevent long times of silence between releases? --Devu 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
Re: [Warzone-dev] Version numbering
On Mon, Sep 22, 2008 at 10:36 AM, Dennis Schridde [EMAIL PROTECTED] wrote: I'd like to hear your opinions, ideas, insights. Maybe you've got a different/better idea how to prevent long times of silence between releases? I like the current way, and do not think we can manage to create releases so rock solid that we do not later wish to create bug fix releases to silence the critics and get less bug reports. After 2.0 we had massive changes and resulting instability in the codebase, making a lot of things no longer work as well as they should. With the new commit guidelines, hopefully this will no longer happen ;-) - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Version numbering
Am Montag, 22. September 2008 11:08:33 schrieb Per Inge Mathisen: On Mon, Sep 22, 2008 at 10:36 AM, Dennis Schridde [EMAIL PROTECTED] wrote: I'd like to hear your opinions, ideas, insights. Maybe you've got a different/better idea how to prevent long times of silence between releases? I like the current way, and do not think we can manage to create releases so rock solid that we do not later wish to create bug fix releases to silence the critics and get less bug reports. My rock stable was targeting at the bugfix releases. ;) But yes, I thought about that too. Some bugs just *will* slip through and might annoy people. My idea was to just ignore that and go on with the next feature release. If someone cares about fixing those in older versions, he could of course backport and do an own release. The idea was to lift the burden of fixing bugs in old versions from the generic developer, so he has more time to work on new stuff. In my dream-world, the x.y releases would come a lot more often than the x.y.z releases currently, which would make it less annoying. Basically what we had in the 2.0 series, just leaving out the 0 from the version number. At least we had full releases at all. And if we can put it onto more defined roads, I think the regression issues during the 2.0 series would not be repeated. After 2.0 we had massive changes and resulting instability in the codebase, making a lot of things no longer work as well as they should. With the new commit guidelines, hopefully this will no longer happen ;-) after 2.0 means in what is going to be 2.1? Commit guidelines: Should it include savegame-versioning (I think that is possible with the .gam format, right?), backwards compatibility, etc? --Devu 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
