DS> For example, what will the "next version" on the 5.1.x line be?
DS>
DS> net-snmp-5.1.2.pre3
DS> net-snmp-5.1.2.rc1
DS> net-snmp-5.1.2
RS> First of all, I don't think any of those would be appropriate for the
RS> current cvs, because they are release names. They need an indication
RS> that they are cvs versions.
Of course.
But if we're discussing using a label such as "CVS leading to next release",
that implies some way of identifying this "next release".
RS> So, the question is given a released version (R), what should the cvs text
(C)
RS> be immediately following the release? Do we want the text to represent what
RS> the cvs *is*, or what it *will be*....
What it is.
We know that with more certainly than what it will (might) be.
i.e.
RS> R 5.1.1 -> C 5.1.1+cvs -> R 5.1.2.pre1 -> C 5.1.2.pre1+cvs
...
rather than
RS> R 5.1.1 -> C 5.1.2.pre1-cvs -> R 5.1.2.pre1 -> C 5.1.2.pre2-cvs
...
RS> I think for a released branch, it makes sense to use that last release +
'+cvs'.
You're agreeing with me again, Robert. I've warned you about that before....
:-)
I'm not sure that we need both the "preN" tag *and* the "CVS" tag, mind.
Particularly if we're going to have some form of counter or datestamp as well.
I'd suggest that something like:
R 5.1.1
C 5.1.1+cvs 2004/06/01
R 5.1.2.pre1
C 5.1.2.pre1 2004/07/01
should be sufficient.
It's not quite as explicit, I grant you, but "preN" and "rcN" code should only
be around for a relatively short period of time. (Especially if the release
master doesn't let himself get distracted by deadlines!)
RS> (side note: I think we ought to use .0 for initial releases- eg 5.2.0.pre0,
RS> 6.0.0. opinions?)
Ummmm...
Not sure about that - I can see the logic certainly, but our current numbering
seems to follow the usual practise in the wider computer industry.
(Or maybe that's changed? <tap, tap, tap> seems to be a mixture :-( )
I don't see the need to change, personally - but it's not something that
I feel particularly strongly about.
Dave
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
