If freenet really needs a way to determine in node interaction has changed, then that should be a different number. Build number can continue to be used for that, but if so, there's got to be another way to determine what build someone is on. A datetime stamp in addition to the build number perhaps. edgar
On Thursday 31 October 2002 05:54 am, Anonymous wrote: > what do you think about making build numbers like for linux kernel? > odd stable and even testing release? > > and *PLEASE* if you make a change in the code, but you think it's not > enough to create a new build, *UPDATE CVS NUMBER*! > > so, may be: > 529 stable > 530 instable > and inside 530 we can see different cvs changes like > build 530 cvs 1.91.0.1 > build 530 cvs 1.91.0.4 > build 530 cvs 1.91.1.2 > ...and so on > > and when you are sure about changes, then you can make: > 531 *STABLE for public purpose and unchangable until 533* > > and in new release announcement you can warn users only if new odd build > found. > (buildnewMOD2) AND (build<buildnew) true or false? > > regards, Anonymous21. _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
