[Meta]

Hello, SA:MP Team (or Kalcor)!
I wanted to ask you how you decide the version number/letter of a new SA:MP Version.

Example: The current version in development is SA:MP 0.3d. But why d and not 0.4?
You know what I mean?

And a second tiny question: Why 0.2, 0.3a, 0.3b instead of 2.0, 3.0, 3.1 ...?

Please answer

Greetz.

[Naruto_Emilio]

Quote:

Originally Posted by Meta Hello, SA:MP Team (or Kalcor)! I wanted to ask you how you decide the version number/letter of a new SA:MP Version. Example: The current version in development is SA:MP 0.3d. But why d and not 0.4? You know what I mean? And a second tiny question: Why 0.2, 0.3a, 0.3b instead of 2.0, 3.0, 3.1 ...? Please answer Greetz.

I think because it's better to use Alphabets, sometimes numbers makes people confused... i think that sa-mp won't release 0.4a till they finish 0.3z. and the z version would be not just awesome... you know man .

[Meta]

yeah, but when they say "Hey, let's name it 0.3d" and not "Hey, let's name it 0.3c R6"?
That's a part of my question, too

[Luis-]

Because it has a lot of updates..

[TheBetaFox]

A huge release changes the subversion. (0.1 to 0.2, 0.2 to 0.3)
A 'major' release changes what's after the subversion, it being either a number, either a letter, either lulz depending on Kalcor's mood (0.2.2 to 0.2X, 0.3a to 0.3b)
A minor release changes the revision (0.3c R1, 0.3c R2)
A beta release candidate version does almost the same thing. (0.3d RC1, 0.3d RC2).

I hope you understand what I mean.

[MaTrIx4057]

Quote:

Originally Posted by Meta Hello, SA:MP Team (or Kalcor)! And a second tiny question: Why 0.2, 0.3a, 0.3b instead of 2.0, 3.0, 3.1 ...? Greetz.

Because it goes 0.1, 0.2, 0.3 ... 0.9 and then only 1.0, made some sense? 1.0 would be stable version without bugs at all.

[Meta]

Quote:

Originally Posted by TheBetaFox A huge release changes the subversion. (0.1 to 0.2, 0.2 to 0.3) A 'major' release changes what's after the subversion, it being either a number, either a letter, either lulz depending on Kalcor's mood (0.2.2 to 0.2X, 0.3a to 0.3b) A minor release changes the revision (0.3c R1, 0.3c R2) A beta release candidate version does almost the same thing. (0.3d RC1, 0.3d RC2). I hope you understand what I mean.

That's the next thing.
What's the difference between a huge release and a major release?
A new function does not declare a "huge release". Remember some big functions added in a Rx Version of 0.3x. It also made a difference of a R Version.

[[03]Garsino]

Quote:

Originally Posted by MaTrIx4057 Because it goes 0.1, 0.2, 0.3 ... 0.9 and then only 1.0, made some sense? 1.0 would be stable version without bugs at all.

Technically it's 0.9 then 0.10, 0.11 etc.

[=WoR=Varth]

Quote:

Originally Posted by Naruto_Emilio I think because it's better to use Alphabets, sometimes numbers makes people confused... i think that sa-mp won't release 0.4a till they finish 0.3z. and the z version would be not just awesome... you know man .

aa, ab, ac ........

[BlazeFury]

Quote:

Originally Posted by Meta yeah, but when they say "Hey, let's name it 0.3d" and not "Hey, let's name it 0.3c R6"? That's a part of my question, too

0.3d represents a new generation rather than 0.3c R6 it'd just evolved..xD