OSDev.org

x.y.z[.s] a.b

x = total redo (75% or more of code rewritten)
y = major (several features become usable or become existant)
z = minor (few things added)
[.s] = sub (updates/patches)

a = alpha/beta (testing cycle)
b = build (how many times _I_ built it)
= unreleased

example:
0.0.1 1.2U - Pre kPutChar in drake
0.0.2 1.4U - Still working on it!
0.0.2 0.5 - Hello world! (future)

now i look at this i notice that i havn't been using [.s] like I should be.... version fix!

I wrote a new paper on my major.minor versioning system, and took the liberty of putting it into the Wiki:

http://www.osdev.org/osfaq2/index.php/MartinBaute/Scratchbook

I'll capture it into static HTML these days and put it on my homepage, but for now I'll keep it where it can be easily edited.

Solar wrote: I wrote a new paper on my major.minor versioning system, and took the liberty of putting it into the Wiki:

Thanks for your designs on versioning. It has given me a lot to think before I (re)start coding again in January.

Then it was already worth doing.

The start of that document is cool: breathe. relax. focus. better now. *rofl*

Have scanned throu it.

Well - for the average test images I release for fellow osdever to take a look at - I have to say, I sometimes release often such test images. But one can't tell that a release, really. It's rather something to play with, test for some minutes to explore what is there. *shrugs*

ON the other points I fully agree: 0.9xx pre1 releases are something for the developers, not for otto normal users. and the thing with the suddenly appearing stunning functionalities instead of lenghty todo lists - as a marketing trick *gg* is an interesting approach. I wouldna question it for it is reasonable.

Gonna look forward to my first *public* release in a few years - a real 1.0 release I daresay. *gg*

beyond infinity wrote: Gonna look forward to my first *public* release in a few years - a real 1.0 release I daresay. *gg*

I think it really points out that developers are always trying to put new things into their code without really finding a 1.00 version. Its the artist versus when is it really complete. From a developer stand point it will never be done. So there has to be a level were people step back from their design and figure out if everything they designed for 1.00 was done, then it is 1.00, if the criteria that was initially designed has been met. Testing is an entirely seperate issue, which should be established before a line of code has been drawn. Test procedures writen before coding forces the coder to place emphasis at meeting the requierments. Solar has definitely put a great deal of perspective into his versioning scheme. I hope to be able to place that sense of control into myown work in the coming days. ;D