argus tarfile naming conventions!

[Yotam Rubin]

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