[Mlview-hacking] version management

[dodji seketeli]

Hi all,

Some ideas about version management of mlview
===============================================

In the near future i propose to open a new cvs branch
for each non devel release version of mlview.
The opening of the branch will be called a "freeze".

When a freeze occurs, no features will be added
in that branch, only bugfixes. Once the freeze is
stable, a major release is delivered. 
The bug fixes that occured in that branch are then
merged in the HEAD so that the coming versions can
take benefits of them.

So what we need now is:

+ define a version numbering scheme to make the 
difference between devel tarballs, non stable version
of a freeze, stable versions etc ....

+ define a way to report the status of the various
branches present in the cvs repository.

+===> maybe create a mailing list related to version
management ?

===
Dodji.

=====
Dodji Seketeli.
http://www.geocities.com/sdodji

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Courrier : http://courrier.yahoo.fr