>It's illogical (to me at least) that 2.0.1_2.0.01 would be NEWER than
2.0.2_1.2.34

At least - this is not the case - or better (if so) this is simply a 
coincidence. It makes sense to me to import tested (or remove failed) code 
from the current dev version in to the stabile one. The most easy way to 
do this is, to use the best tested dev version as the last stabile one.

And - don't forget : every time I have to maintain 4 versions (some times 
even more) - the published stabile 2.0.1, the published dev 2.0.2 (both 
with files, plugins and modules) and at least two working versions (one in 
dev one in test). There are also more than 100 sample, test , code 
analyzing, regex analizing and benchmark routines - all of them uses the 
same version numbering schema.

A change of the version numbering logic is only possible of a new version 
will need new requirements (for example Perl 5.12 or a needed C compiler). 
In this case the autoupdate feature will stop working for all older 
versions.

Thomas

 



Von:    K Post <nntp.p...@gmail.com>
An:     ASSP development mailing list <assp-test@lists.sourceforge.net>
Datum:  17.11.2010 19:59
Betreff:        Re: [Assp-test] fixes in assp 2.0.2_2.0.01




Just a suggestion-

Version numbers with ASSP have always been strange.  Now, I know that
there's the whole odd/even stable/dev schema, but this isn't simple.

I suggest releasing this not as 2.0.1_2.0.01, but instead as something 
like
2.1.0000.

It's illogical (to me at least) that 2.0.1_2.0.01 would be NEWER than
2.0.2_1.2.34

If you always had a .0000 be the stable release then you could have dev
releases increment that number.  So for example

2.1.0000 could be the stable release (same as 2.0.2_2.0.01).  We'd know 
this
is stable since it has 0000

Then when a bug is found or feature is added, we'd goto 2.1.0001, then
2.1.0002.  We'd keep incrementing until a new stable release is ready. 
That
would become 2.2.0000.

Just my thoughts....
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to