FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: February 14, 2003 2:43 PM
> Il ven, 2003-02-14 alle 17:17, Jayaraman, Gautham ha scritto:
> > hi
> > 
> >         I was trying to install the freetds0.61 (nightly snapshot)
> > second time around. Now when I again installed with 
> freetds0.60... Its
> > working fine!!!
> > 
> I think snapshot are 0.62 (future version), not 0.61, so you have this
> problems...
> If you have CVS access checkout BRANCH0_61 branch (cvs checkout -r
> BRANCH0_61 freetds)

It's a little confusing....

The nightly snapshot (from MAIN) reports itself as 0.61.  That's derived
from:

$ grep 61 configure.in
AM_INIT_AUTOMAKE(freetds, 0.61)

The rc1 reports the same.  The only way to tell them apart is to know which
tarball you used, or "head ChangeLog".  

Perhaps this would be a better policy:

1.  When branching a release, edit configure.in to reflect the branch's
status e.g. "AM_INIT_AUTOMAKE(freetds, 0.61rc1)".  Update as necessary,
creeping to 0.61.  

2.  Simultaneously in the MAIN branch, bump the point release by five:
"0.61.5".  This leaves room for point fixes to the release branch.  On this
project, we've only ever had one point release.  If we need more than 4,
we'll have more problems than just getting the version numbers right.  

3.  "0.61.5" (a/k/a current) can be bumped willy-nilly as long as it stays <
0.62.  When it's time the 0.62 release rollout, branch the code, set the
branch's version to 0.62rc1 (or pre1, as appropriate).  

etc. Is that good?  Other suggestions?  How do other projects manage this?  

When we know what we want, I'm happy to bring the current situation into
conformance.  

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.