> 2) I never liked the 5.2.pre0 idea because we were never sure what the
> next version would be.
I think that's still the case, in fact.
For example, what will the "next version" on the 5.1.x line be?
net-snmp-5.1.2.pre3
net-snmp-5.1.2.rc1
net-snmp-5.1.2
(and could we have predicted this two weeks ago, immediately after
the 5.1.2.pre2 tarball was prepared)
The only time when the "next version" is predicatable will be
immediately after a full release - when we could start looking
ahead to the next release. I.e. net-snmp-5.1.3.pre0
But it feels a bit premature to start talking about that
quite so quickly.
> As far as
> a vote for what to use, I think either VERSION.cvs or VERSION.pre0
> makes the most sense. probably .cvs would be my vote, but I'm
> fairly on the fence.
I'd agree with that.
This also leaves the VERSION.preN tag available for the pre-release
run-up itself.
What about the other question - whether to include some sort of serial
number or timestamp as part of the CVS version? And if so, how
frequently to update this?
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
