On Thu, 01 Jul 2004 10:25:32 +0100 Dave wrote:
DS> > 2) I never liked the 5.2.pre0 idea because we were never sure what the
DS> > next version would be.
Good point. I had forgotten major version bumps. Of course, there's no reason
to think of the cvs version text as a serious commitment. If we change it to
5.2.pre0 once the 5.1 patches branch is created, and 3 months later we decide
the next elease is going to be 6.0, we just update the text.
(side note: I think we ought to use .0 for initial releases- eg 5.2.0.pre0,
6.0.0. opinions?)
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
DS>
DS> (and could we have predicted this two weeks ago, immediately after
DS> the 5.1.2.pre2 tarball was prepared)
First of all, I don't think any of those would be appropriate for the current
cvs, because they are release names. They need an indication that they are cvs
versions.
So, the question is given a released version (R), what should the cvs text (C)
be immediately following the release? Do we want the text to represent what
the cvs *is*, or what it *will be*....
is R 5.1.1 -> C 5.1.1+cvs -> R 5.1.2.pre1 -> C 5.1.2.pre1+cvs -> ...
vs
will be R 5.1.1 -> C 5.1.2.pre1-cvs -> R 5.1.2.pre1 -> C 5.1.2.pre2-cvs ...
And in answer to Dave's original question, as I mentioned above, I don't see a
problem with releasing something other than what the cvs text was implying. eg
R 5.1.1.pre2 -> C 5.1.2.pre3-cvs -> R 5.1.2.rc1 -> C 5.1.2.rc2-cvs
And if 5.1.2.rc1 proved to have no show-stopper bugs, then it could later be
re-tagged, updated to 5.1.2, and released.
I think for a released branch, it makes sense to use that last release +
'+cvs'.
--
Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/>
<irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
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
