Mini guide on version numbering...

[Chippiewill]

A couple of people aren't using logical version numbering. There is no set rules on it but here's a small suggestion.

X.Y.Z

X should be changed when you do a complete re-write or re-design of a layout/script, this is also known as the version number

Y should be changed when you add a new feature or colour scheme

Z should be for things like bug fixes, security updates or wording changes

Other notes:

Before the first 'Golden' (unnoticable bug free) release it should be like

0.Y.Z

[MrCraig]

People can number things which ever way they want?

[eg]
My current hsoft usersystem v is 2.1.0R1 ...

[Chippiewill]

Yes, but for those who go insane

ie if a person puts the first version as V28473.4524.42543

Doesnt look right

[Awfy]

Good for making a base for version numbering but some of the world's major companies such as Apple, Skype, Google, Microsoft all number their versions completely different.

[Chippiewill]

I know it's just a suggestion for those who are unsure as for what to do.

@below tyvm

[Forge]

Very useful pal +Rep

[Luckyrare]

Like most software its usually major.minor.revision


The thing is not to do so many revisions, if your releasing an update you need to make sure its a decent one. Thats why I prefer using Nightly, Alpha, Beta, Gamma and Gold. You dont as such need to release each major update under those names but its good to keep tabs on what your working on otherwise you will annoy people with tiny worthless updates. New features should only really be added on the major releases, imo.

[Chippiewill]

Of course you could do the ubuntu way


Y.M

Y = Year released
M = Month released

They have nick names as well like breezy badger