Perhaps 0.58 beta1 will be the only release for 0.58 and 0.59 will directly follow. For some versions (perhaps 0.58, how knows?), there wont be much more versions. For smaller changes/fixes, we will stay at one version and make just a new release (0.58 beta1 was the last release of 0.58, so next would be 0.58 beta2). For bigger changes, we will make a new whole new version (e.g., last is 0.58 now, so next would be 0.59). This was the main reason why we often waited so long with a release - because there were known problems and it was not stable enough for us.) We/I always tried to make the beta release not really a beta release but a stable release. There are known issues and we don't try to make them as stable as possible. A beta release is, as the name says, a beta release. If we want you to test something, we will create a new beta release. There wont be any SVN/Git nightly builds anymore. We will make releases far more often (only if there is something to release of course). Now, this is how we plan to organise in the future: They are not complete yet but they have helped me a lot already (for the 0.57 rc1 and 0.58 beta1 release). I have created a lot of distribution scripts which will make the whole releasing process a lot more easier and mostly automatic. If you want to get an impression, look here, at the bottom on the page under heads (that are our main branches): The master is always the most up-to-date code, it's probably the code for the 0.59 version or whatever we call that one. We have already 3 main branches at this time: One for 0.57, one for 0.58 and the master. This will make the code management a lot easier and allows us to easily maintain several versions (these are called branches). Several things have changed now internally which will simplify that a lot: This can take a whole weekend of annoying work of at least two of us at the same time.) For every supported system, it has to be compiled, tested, packed together and uploaded to SF and if something was forgotten, the procedure has to be started from the beginning - sometimes even for all systems again. The main problem about this was that is was very complicated to maintain/work on multiple versions at the same time and to build up a release itself. We planned since a long time to make releases more often. Some explanation what has changed recently: Here are all files for Windows, MacOSX, Debian and the source release (for Linux): So I hope we have a good and stable release here. (not much despite the bad network performance was reported for 0.57īeta8). Note that most bugs of 0.57īeta8 are also in this release - though there shouldn't be that much If you have any problems, please report so. Uploadbandwidth should be fixed hopefully here. This 0.57 rc1 is basically a slightly fixed 0.57 beta8. If you see any other problems, please report them. Some of the issues are already described here: Version and there are a lot of new and nice things to discover, but I386, Debian/Ubuntu amd64 and source code) can be downloaded here: select weapons ingame (chat command /weapons)Īll files (currently Windows, Windows patch, MacOSX, Debian/Ubuntu physics should be exactly like LX56 now worm speed/damage/shield/friction factor hit/damage yourself/teammembers can be enabled/disabled (aka friendly fire on/off) game size factor (you can make everything bigger or smaller) extended physics engine / gamescript (still in development) ingame console much more advanced, many new commands, better autocompletion ingame console can be used everywhere, also in menu damage reporting (shows how much you injured a worm) uploadlimit check fixed + automatic measuring of speed This contains basically everything we worked on since 0.57 beta8. OpenLieroX 0.58 beta4 jumped number from last release of 0.57beta8, which represent the work they done in past year
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |