FreeTDS Development Group

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

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: September 13, 2002 2:12 AM
> 
> What about branching CVS in a HEAD and stable tree ??

<personality>
After 20 years at the keyboard (rounding up somewhat), here's my view of the
development process:

        while(it matters) {
                code    
                code
                code
                draw a line
                release
        }

IOW, a linear repetitive process.  I think of CVS labels as milestones (or
cracks in the sidewalk, depending).  As Ronald Reagan said, "The past is
past, and the future is yet to come."  OK, so you know where I'm coming
from?  
</personality>

The line-in-the-sand approach is easier for the developer and harder on the
user.  Our "support" plan boils down to, "You don't like the release?  Then
use the snapshot."  On that score we could do better.  

I think branching now would be counterproductive, and I can't think of
anything wrong with 0.60 that can't be fixed at the head and released sooner
rather than later.  

That said, Frediano is right in principle.  Next time we release, I'd like
to do it by forming a CVS branch.  That way, if there are to be updates that
we care to offer to that release, it will be relatively simple for both user
and developer.  

Is acceptable?

--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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.