Page 1 of 1

Helping Warzone 2100 with more stable releases

Posted: 26 Apr 2012, 03:50
by Staff
In order to try getting more stable builds, we need a bit more help before we do beta releases.

We have a automated build process that generates nightly (sometimes sooner), both linux (tarball) & windows (installer) builds.

http://buildbot.wz2100.net/files/bugfixes/ (This is the main bug fixing branch that will be merge to both master & 3.1)
http://buildbot.wz2100.net/files/3.1/ (this is where the next beta comes from)

We also have master builds available here http://buildbot.wz2100.net/files/master/ that is much different from 3.1, and is testers are badly needed for this version!

When we fix things, it gets put into bugfixes, and then it is merged to both master & 3.1
When we have specific things that should NOT be in both master & 3.1, then we only update the required branch, and not bugfixes.

There is sometimes lots of activity, as can be shown here:
https://github.com/Warzone2100/warzone2 ... s/bugfixes
https://github.com/Warzone2100/warzone2100/commits/3.1

Currently, the only disadvantage of getting these builds is, that it won't work with the next newer build, and also, if you play multiplayer games, everyone needs to have the exact same build or you can't connect.

For example, a windows users gets http://buildbot.wz2100.net/files/bugfix ... de0c41.exe then the linux user must also get the same revision http://buildbot.wz2100.net/files/bugfix ... c41.tar.gz

[linux only section, for those that are not afraid to compile things]
Spoiler:
Hope that makes sense.

As far as testing goes, it is pretty difficult to know exactly what might have been broken again.
You can get a rough idea by looking at the activity of what is going on, and see if a certain thing that says was fixed, is actually fixed.
If it isn't fixed, then reopen the ticket again, and tell us!
If you find a new bug, then open a ticket http://developer.wz2100.net/newticket and tell us!

*thanks to NoQ for spotting a typo. (Will be pruning posts based on content, and how it relates to this subject.)

Re: Helping Warzone 2100 with more stable releases

Posted: 05 May 2012, 16:17
by cybersphinx
I think we should only have bugfixes here, since 3.1 lags behind that (the automerge currently runs Monday and Friday 8:00 (master) / 8:10 (3.1) server time (CE(S)T)).

Re: Helping Warzone 2100 with more stable releases

Posted: 05 May 2012, 23:35
by crass
doing a autopatcher would really help testing!

Re: Helping Warzone 2100 with more stable releases

Posted: 06 May 2012, 02:54
by vexed
crass wrote:doing a autopatcher would really help testing!
There is no cross platform way of doing it at this time.

Re: Helping Warzone 2100 with more stable releases

Posted: 05 Jun 2012, 13:56
by Urnight
thanks for the hard work of making a free game for us to enjoy :)!
also who ever made that new built in AI, it's amazing. They even tower rush sometimes xD

Re: Helping Warzone 2100 with more stable releases

Posted: 13 Aug 2012, 07:25
by Staff
A reminder, we still need people to test things out, and unfortunately, it seems nobody is bothering trying to help us produce more stable builds by getting one of the nightly builds, and testing them out, and reporting issues with them.

Currently, we are trying to get a Release Candidate up, but ran into some issues. :stressed:

Remember, bug reports belong on trac. http://developer.wz2100.net/newticket
If you have comments about possible bugs, then post in the gameplay section of the forum, under the appropriate area.

At the time of this post, the latest build we have for 3.1 is http://buildbot.wz2100.net/files/3.1/wi ... 6084f4.exe

Remember, everyone MUST have the same version if they play multiplayer.