OK. Two things then: 1) Thinking long term, what about modifying the 3-4 plugins to use a more reasonable numbering system in v2? Or if to complicated, maybe change the way we refer to versions in human readable mediums (messages, version reporting, sourceforge etc), but still keeping the numbering system internally the same?
2) On the odd even thing, before 2.0.1 went gold last month, didn't we have a 2.0.1 RC 0.5.xx version that was DEV? That's a 3rd number being odd, but it was dev. None of this is that important - just figured I'd make the suggestion to help improve this already awesome program any way I can. On Mon, Mar 15, 2010 at 2:19 AM, Thomas Eckardt <[email protected]> wrote: > Changing the version numbering in V1 is possible - but not easy to do > because of the running autoupdate feature. > In V2 this is more complicated, because the plugins are checking the ASSP > version number to detect if they are compatible to the running version. > I think it is realy easy. Than higher the number than newer the version. > The third digit determines if it is a production/public version ("odd") or > dev version "even" . > > Thomas > > > > > Von: K Post <[email protected]> > An: ASSP development mailing list <[email protected]> > Datum: 14.03.2010 23:59 > Betreff: Re: [Assp-test] version number suggestions > > > >>We think that the 8 digits are needed for our work. > > Ok, then how about using something a bit easier to interpret visually. > > 2.0.2 1.00.02 is just too many dots > > You're used to seeing your version numbers, but can you quickly and > easily tell me the order in which these versions were released? > > 2.7.8 5.15.18 > 2.8.0 1.01.99 > 2.7.9 1.02.98 > 2.8.0 0.02.15 > 2.7.7 9.99.99 > 2.8.0 0.30.11 > > Sure, it's doable like that, I just think that it's easier to see it like > this: > > 2.7.8 51518 > 2.8.0 10199 > 2.7.9 10298 > 2.8.0 00215 > 2.7.7 99999 > 2.8.0 03011 > > especially when the first x.x.x is the same during the development > process: > > 2.8.0 03512 > 2.8.0 05215 > 2.8.0 05115 > > Isn't that easier for you to see? > > 2.0.2 10002 is much easier to read IMHO. 2.0.2 is the base version > with 10002 essentially being the build. > > Then when we're talking builds in this disucssion list, we could just > say 10002 and it's clear what we're talking about. > > I'd still like to see devel or public listed, but if that's not > possible, so be it. > > 2.0.2 10002 dev > > vs > > 2.0.1 10002 pub > > It looks like assp.pl is already hard coded whether it's devel or not, > in determining which cvs to grab updates with. Why not just have it > set dev/pub there and display it in the console. And, it shouldn't be > hard for you to list dev/pub on sourceforge. > > That's what I think. Thanks for everything. > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Assp-test mailing list > [email protected] > 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! > ******************************************************* > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Assp-test mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
