Upcoming Version Numbers (What do you mean, 2.0 and ME?)

[Mystic]

Okay, we've been getting a complete asston of questions about this, so it's time to clarify:

We are fixing the version numbers for SRB2 with ME. For the past 6 years, we have been calling the "final" version of SRB2 "1.1", which has created a few quirks in the version numbering as we get closer and closer to 1.1 without actually getting to it. However, since we've had about 15 releases that were supposed to be the "last" release of SRB2 before the final version, I think it's time for us to admit that we honestly don't know when the final version will come out and stop giving the final version a version number before we even get there.

Hence, we're starting over. SRB2ME is SRB2 v2.0, because it's a huge revision to the game and we're going to start using version numbers like everyone else. New versions will be using the following scheme: 2.<major>.<minor>. Henceforth, if there is a bug we need to fix in ME by a release, we'll release v2.0.1 (no major revision, first minor revision). The next major release after ME will be called v.2.1 (first major revision, no minor revisions on top of that), and if there's a bugfix in 2.1, it would be called 2.1.1.

There is no "final version" number. 2.1 is not necessarily the final, and neither is 2.2. All version numbers mean now is what they're supposed to mean, which version it is. I hope this clarifies what all this means so we can get back to our sanity on this regard.

 

[Chibs]

I guess this means that 40% of the userbase in no longer utterly confused.

 

[Prime 2.0]

Naw, I'm sure at least that amount still thinks SRB2ME was "May edition", and think that it's now called SRB2 Sage Edition. Maybe even AFTER reading Mystic's post.

 

[Chibs]

Quite sad, actually. I guess that's what happens when one keeps changing the names of the next release.

...No offense.

 

[Flame]

Are we going to be reliving the 1.09.3 era?

 

[Mystic]

No, Flame. All that's happening is we're switching to a version scheme that makes sense instead of the absurdity we've been using for years. It just so happens that 1.09.3.x was a period of time when our version numbers made sense.

 

[Rob]

Nothing made sense about the calamity that was 1.09.3. :(

 

[Mystic]

No, Rob, the version numbers made perfect sense. You looked at the last number and that was the version of 1.09.3 you had. If that number was smaller than someone else's, you need to update.

 

[Jellybones]

This should have been posted when it was decided, so that (almost nobody) asked in the first place. But better late then never, right?

 

[Mystic]

Well I thought it was fairly obvious, but apparently it wasn't.

 

[glaber]

some time what's obvious to one is not obvious to another. That's why I have trouble finding stuff that's sitting right in front of me.

 

[fox Unit 01]

You think that was bad, take a look at how awful my use of the "Release Candidate" has gotten (just look at length of that changelog). At least you guys were sticking to real version numbers, instead of "Beta RC" crap. ;P

 

[sonicfreak94]

some time what's obvious to one is not obvious to another.

Thank you, Captain Obvious!... owai--*shot*

Aaanyway, this is good I guess, even though I wont remember how those numbers work in about 5 minutes =P