Last month we put a news item out about our retention policy. We have decided to start actively enforcing this policy from the 1st of March.
This is needed to maintain proper stability of our services. Each night a 03:00 UTC our server will cleanup any files that are outside of the retention policy.
To be sure we don't lose builds that are needed we have a copy of the current data available. Should you feel like a build (for this first month) has been removed in an incorrect way we can verify our logs and fix any issues that should arise. We have run our cleanup script on a dry run for some period to prevent such errors. Should they occur contact us through IRC.
This version brings some major changes compared to the 0.3.x versions:
There's numerous other fixes, changes and additions. For a full changelog, see http://bundles.openttdcoop.org/nml/releases/0.4.0/changelog.txt
Get the latest release version from the bundles server: http://bundles.openttdcoop.org/nml/releases/LATEST/
Note to package maintainers:
As you may have noticed our services have received some outtage. This happend during a maintenance that was required for needed security updates related to CVE-2015-0235 (the glibc story / http://www.openwall.com/lists/oss-security/2015/01/27/9). When we rebooted the server the most scary thing happend for us. Our server did not return online. After some help from our hosting provider we managed to log back in.
To make the most out of this situation we immediatly also starting converting some of our local containers to a diskimage format (PLOOP / https://openvz.org/Ploop/Why). However because one of our main containers which has all the HG repositories has so many small files this conversion is taking longer then expected.
We want to apoligize for this situation and are waiting for this container conversion to finish. After this the most critical containers should all have been converted and most of the other ones are related to non-development stuff that should have no extended downtime like this.
Ladies and nutmen,
just now I am realizing I forgot to officially mention that I have been working on another project for the past months. RAWR Absolute World Replacement is currently 32bpp/ExtraZoom LANDSCAPE with ROADS and TRACKS. Eventually I am hoping to replace all the sprites the game needs, and the final output then could be a full base set.
Visually, the set is obviously 32bpp/ExtraZoom which looks relatively nice. Functionally, it lets you choose from the 4 climates and force any of them visually. That way you can apply any of them you want – especially if you load the newGRF as a static one. I hope you like it, there is still a lot of things to be done, but the core is there.
The project home is at the devzone per usual – you can also find a guide on how to apply static NewGRFs. I also have a thread at tt-forums, you are welcome to contribute/place your impressions/screenshots there
You can download RAWR from the online content – BaNaNaS – through the game, or from the website manually.
Enjoy and let me know what you think!
In recent months the retention policy for builds created by the DevZone's compile farm was rather liberal and all build for every push were kept. However, with the increasing size of NewGRFs (we needed to upgrade the allocated space for builds several times already) we need to go back to the original retention policy:
Nightlies are not built specifically anymore. But once a day, the build from the most recent push will be promoted to a nightly build.
See also our wiki page at UsingTheCF which documents the data retention policy. If you need one of the old nightly builds or push-builds, then please grab it now. The new build management script will be switched on in the coming days.
Hell000 and Merry Christmas! We are happy to announce that our inner circles have gained yet another person, Hazzard!
Being around for a long while, most of you probably know him, but if you don’t, Hazzard is a great builder and person. His logic mechanisms and other construction put your brains in greater hazard when you see them. He has been generally very helpful, teaching people, being a nice person, and everything else.
Everybody, please welcome Hazzard to the openttdcoop members club!1 Comment
Due to the increasing size of some projects we changed some settings in the compile farm itself, in Jenkins so that build results will not be kept any longer on that build server. As previously all build results will always be published to our file server at http://bundles.openttdcoop.org. The results of the latest build can always be found at http://bundles.openttdcoop.org/PROJECTNAME/push/LATEST (where PROJECTNAME is the name as it appears here on the DevZone, which is also part of the repository URLs)
As one of the sysadmins of #openttdcoop alot of work happens for me on the background. Most changes go unnoticed, some cause minor breakdowns (sorry ;)) but alot of changes you don’t see. The changes that mostly did go unnoticed were changes to our mail infrastructure, database updates, backup procedures. And that’s just a few.
Today one of the changes that you will see is a change to our paste service. The paste service as it currently is has changed. We have switched to a new backend which was needed. The old pastes are NOT deleted. They can still be reached at http://old-paste.openttdcoop.org. However do keep in mind that this will go offline at some point and we strongly advice against creating new pastes there.
Our new backend is currently live at https://paste.openttdcoop.org. In this case we are using sticky-notes as a backend. This gives you more privacy and options compared to the old paste. We do hope the new features help everyone out even us as admins in maintaining it all.
Another change that already is active (and you might not always notice) is a replacement we did for our bundles server. This had to happen at some point. And today it is done. This change won’t have much of an impact. But we hope to improve response times with this new server.
These are just a few of the changes you’re going to see. More will follow at some point but this is just a start
Should you have any questions join in on IRC (#openttdcoop @ OFTC or through http://irc.openttdcoop.org)No comments
Ladies and madmen, I am happy to announce that the project I have been working on for the last few months, has grown to it’s first release! First of all I would like to give a huge thanks to frosch who helped me greatly to get the production mechanism working, but also Alberth for trying to help me as much as possible. I would also like to thank all the people like planetmaker for answering my endless and often stupid questions about NML in general. I greatly appreciate everyone who have supported me with any feedback!6 Comments
Today Alberth and myself changed the required python version of NML nightly versions and a future NML 0.4.0 to python 3.2 or newer as python2 is slowly phasing out, and also the imaging module is better supported with python3. For some time there will continue be updates to the 0.3 branch as well with an occasional maintenance release, though.
If you're on windows, this is of little consequence to you, we continue to provide an exe file which can be used out-of-box, now based on python 3.3.
If you're on OSX or linux and use nmlc from a repository checkout, you'll want to use the package manager of choice and install python3 and python3-ply and python3-pillow (or called python3-imaging or similar).
If you encounter any problems, please let us know
Also package maintainers may consider to already look into updating their dependency lists accordingly
Alberth & planetmaker