On Thu, 24 Jun 2004 13:36:44 +0100 Dave wrote: DS> Thomas> BTW, shouldn't snmplib/snmp_version.c in CVS MAIN now have DS> Thomas> const char *NetSnmpVersionInfo = "5.2"; DS> DS> Robert> I'd actually prefer something that indicated cvs, DS> Robert> too: "5.2.0-cvs", or "pre-5.2.0-cvs". DS> DS> Robert> The other developers don't agree with us. DS> DS> I'm not quite sure where you got that idea from, Robert. DS> I'd also prefer to see an indication that this is a CVS-based version DS> of the code.
On Thu, 24 Jun 2004 15:08:17 +0200 Niels wrote: NB> I fully agree. The first thing I do after running cvs update is to patch NB> snmp_version to say 5.1.2.pre2+yyyy-mm-dd Well, I could have sworn I had brought this up before, and been shot down. Since we have agreement for 3 of the core developers, let's see if we can come up with a format we agree on while we wait for any objections. I see at least two questions: 1) How to identify the cvs branch. a) based on previous release (5.1.1-cvs/5.1.1+cvs) b) based on next release (pre-5.1.2[-cvs]) c) based on branch tag (v5-1-patches) d) ?? 3) If/How to identify branch version. Give XXX from (1) above, a) XXX[+-]yyyy-mm-dd b) XXX[+-]n, where n is incremented [daily|weekly|manually] c) ?? -- 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
