Re: [ng-spice] Codenames
On Thu, 15 Jul 1999, Daniele Foci wrote:
> Il 15/07/99 13:35, Paolo Nenzi ha scritto:
> > I am planning to release the future versions of spice (ng-spice) with
> > codenames, to distingush them. Due to the meaning of the word 'spice', I
> > am planning to use spices names:
> > chli, pepper, etc. etc.
> Are you crazy? :-)
>
> You can use these names only for stable release (max 1 for year), as Debian
> teach: 1.0 Chili, 2.0 Pepper, etc.
Well, spice version will remain 3f5 as soon as we do not decide that the
changes have wiped out most of the original structure.
> For unstable release, better use standard names:
> 1) 1.1 - 2.1 - 3.3
Michael Widlok (the one who is currently fixing some pieces of code in
poland) has adopted the following naming scheme:
spice3f5-<fx>
where x is the fix level.
> 2) 990702 - 990822 <--- best choice (also for snapshots)
Aaagh, i hate these kind of versioning, I prefer vthe Oracle suystem:
You can buy Oracle 8.7.12.6.34a.6.7.35.
Seriously,
we can use the following scheme:
Major Release: New fature added, or relevant code changed.
Coding: chili, pepper, berbere', paprika, etc.
Minor Release: Cleaning up of the code or relevant bux fixing.
Coding: <major name>-{1,2,..,n}.
Bug Fix: Small bug fixing.
Coding: <major name>-{minor number}-fix{1,2,..,n}.
Snapshot: While this program will not be released as ng-spice, there will
not be much difference between snapshot and other type of release. When
the product will start to be interesting, the most relevant feature of
ng-architecture will have been added, the we shoul revert to a more
standard naming scheme.
What d oyou think of the naming scheme ?
By the way, we could start already with what Daniele proposed, but there
will surely be more than 1 major release er year, we are not Debian ;-)
Paolo
Partial thread listing: