argus tarfile naming conventions!

[Chris Newton]

I like this too... and, a lot of people (in the linux world) are familiar with 
it.  All of us bleeding edge types, can run the 2.1 series, and fixes that are 
required for 2.0 that have been tested well in 2.1 can be back ported to 2.0, 
then shipping out 2.0.x releases.  Obviously not all changes in 2.1 will be 
back ported to 2.0, but anything important/needed can be.  Stuff that is a 
fundamental change in 2.1 only becomes a stable version when you release 
2.2.0.
  All odd # x, in 2.x.0 is devel, all even are stable.

Chris

>===== Original Message From Yotam Rubin <yotam at makif.omer.k12.il> =====
>Greetings,
>
>We can do what a lot of projects do: Create a branch for the stable
>version and a branch for the unstable version. Example:
>We would label the stable branch as 2.0* and its development (unstable) 
branch
>would be called 2.1*. This provides a method to clearly distinct between the
>two versions. An added bonus is that this does not cause problems with 
packaging
>software.
>
>	Regards, Yotam Rubin
>
>On Thu, Apr 05, 2001 at 09:18:12PM -0400, Carter Bullard wrote:
>> Gentle People,
>> There doesn't seem to be much opinion on patches
>> and how we should distribute, etc....
>>
>> The best strategy for managing changes is to rely on
>> CVS, but everyone is not into CVS, so a tarfile of the
>> current project status is important.  This will be
>> in the ftp://qosient.com/dev/argus-2.0 directory
>> and official links on the argus web site.
>>
>> So now for the hard part, naming conventions.
>>
>> Suggestions for naming the development tarfiles!
>> argus-2.0.1.alpha.1?  argus-2.0.1.dev.1? moving to
>> argus-2.0.1 at release time?
>>
>> I would rather not generate a patch file until the
>> next release is "official".  Except, of course,
>> for emergency purposes to distribute fixes to
>> particularly nasty problems.
>>
>> Is this reasonable? I'd like to put the next mods
>> up this weekend, so your comments would be greatly
>> appreciated!
>>
>> Thanks!!!!
>>
>> Carter
>>
>>
>> Carter Bullard
>> QoSient, LLC
>> 300 E. 56th Street, Suite 18K
>> New York, New York  10022
>>
>> carter at qosient.com
>> Phone +1 212 588-9133
>> Fax   +1 212 588-9134
>> http://qosient.com

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Chris Newton, Systems Analyst
Computing Services, University of New Brunswick
newton at unb.ca 506-447-3212(voice) 506-453-3590(fax)