argus tarfile naming conventions!

[Carter Bullard]

Hey Yotam,
   Ahhhh, convention.  So the strategy would be that
there now should exist 2 branches, 2.0.1 and 2.1.0.
Patches are going into 2.0.1 and new development
goes into 2.1.0.

   Is there a convention for merging the 2.0.x into
the 2.1.0 work?  Does, "merge when only when the minor
version is released" sound reasonable?

   Tarfiles for 2.0.1 testing will be similar to what
we were doing before, but no letters this time.
So I'll put up argus-2.0.1.beta.1 on the dev/argus-2.0
ftp site today if anyone wants to do some testing and
I'll send some mail to the list.  When we're pretty happy
with it, I'll announce and replace on the web site.
No more than 1 minor release a month but hopefully
the mean will be 3-4 months.

   Thanks for the suggestions!!!!!

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

> -----Original Message-----
> From: owner-argus-info at lists.andrew.cmu.edu
> [mailto:owner-argus-info at lists.andrew.cmu.edu]On Behalf Of Yotam Rubin
> Sent: Friday, April 06, 2001 8:57 AM
> To: Argus (E-mail)
> Subject: Re: argus tarfile naming conventions!
> 
> 
> 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
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20010406/f47c7a00/attachment.html>