In the meantime, which github branch should we mere mortals be building from? Maintenance/1.77 or Master?
That depends what you want. Maintenance/1.77 is what will become 1.77.1 (and then later 1.78). It's also the one which the Mac nightly builds are already coming from. If you're wanting to help us by providing bug reports to improve the quality of the next Oolite release, or you're just wanting a version without some of the bugs which were in 1.77, then that's the one to use.
Master is on the path towards 1.79 and is very much at the "breaking things" part of the release cycle. If you want to try out some of the latest features, feedback would be very welcome, but I wouldn't recommend it for actually playing the game, and many of the current bugs are a case of "not finished writing that bit yet". On the other hand, if you want to submit patches to the Oolite code, that's the one you'll need to write them against.
If you're wanting to help us by providing bug reports to improve the quality of the next Oolite release, or you're just wanting a version without some of the bugs which were in 1.77, then that's the one to use.
That, and the idea of ending Cody's sobbing..
cim wrote:
Master is ... very much at the "breaking things" part of the release cycle. ... many of the current bugs are a case of "not finished writing that bit yet".
And those would be my main reasons for avoiding Master at the moment..
Many thanks for the clarifications.
Most games have some sort of paddling-pool-and-water-wings beginning to ease you in: Oolite takes the rather more Darwinian approach of heaving you straight into the ocean, often with a brick or two in your pockets for luck. ~ Disembodied
Any progress on this for Windows users, Admiral? I'm missing the nightlies badly!
There are a few pending issues before we are ready with this and at the moment things like summer holidays, me being for the last three months in the United States etc, are getting in the way of finalizing it. The main issues are modifying the installer scripts to collect their information from github instead of svn and, of course, adapting the nightly server scripts so that they do their magic using github instead of Berlios - and verifying that all this actually works. I don't think it's terribly complicated business, but we need to find time for coordinating the migration and actually doing it and I'm afraid this time is not yet.