Hi guys,

In my opinion there are enought improvements to make a 0.78. I would like to make something like a beta release soon, but there are still some bugs left which needs fixing (especially the drawing bugs in CA and THIS).

I also want to retry this release-from-a-branch thing, which doesn't worked well in the last release, maybe it will work better this time. When the known bugs are fixed, I will create such a branch. It will help if you would follow these three simple guidelines:
a) please don't commit anything to the branch, I will do this
b) make small commits (should be done anyway)
b) give usefull commit messages, so I can see if its a experimental new feature, or a small bugfix

If you think that a particular patch should (not) be merged in the branch, feel free to tell me via the regular ways(mantis, forum pm, lobby etc.).

Thanks

Yay. Thanks for trying to stick with the release-often model, I don't think 0.77 was a typical release. I suspect that, given the bug-fixes already in SVN, it will be welcomed.

I vote we call this 0.8 and quit the whole 0.xx tiny increment stuff. At this rate we'll reach a point where spring 0.79945 will be replaced by a major release called 0.7994501

It is a little weird yeah, considering 0.67 -> 0.70 was the switch to multiplatform code, 0.78 suggests spring has only added some simple features since 0.70, ignoring the huge improvements in lua scripting.

0.78 - 0.70 > 0.70 - 0.67

But I wouldn't mind bumping an extra 0.02 to 0.80

Or we could just drop the 0. and release Spring 78.

The spring version number is not a real number, it's a special kind of primitive

We used to treat the 0.ab version number more like a 0.a.b version number, because it went from 0.40, 0.50, 0.51, 0.60.

"0." + major + "" + minor + "b" + bugfix
Best. System. Ever.

<Peet> lurker, post in the feature freeze thread that since the 0.6->0.7 transition occurred because of the major addition of multiplatform support, 0.7->0.8 needs its own new huge feature other than lua, which did not result in a major version change
<Peet> then yell at jc to finish sm3

imo 0.8 should be reserved for fully functional multi threading.

I'm fine with any version number as long as it's strictly higher than current stable.

Isn't multithreaded rendering/sim whats currently being fixed in trunk? That if not the brand new AI interface makes for more than enough of a change.

that reminds me - the plan is still to merge the new interface in before release, right?

Indeed, it is critical that the new AI interface is pushed out as soon as possible

I don't suppose that things will get wrapped up before Christmas? I need to make a decision about RC4 here, and I don't want to ship an obsolete version of Spring.

Good work, guys. I don't think we need any more minor release (no 0.78.3), maybe a 0.78.2.2.

Oh, and I would like to make the next major release in march / april / may.

there's one evil bug - mantis 1286, possibly related to air bases, but nothing is certain. fixing it would warrant a bugfix release IMHO.