On Fri, 2005-01-07 at 15:23, Robert Story wrote: > DS> (I was a bit surprised to see that you'd applied this > DS> to the 5-2-patches line as well, since I thought that was > DS> currently in pre-release freeze, but that's by-the-by). > > I thought comment changes were always fair game. And comments in > mib2c conf files seems even safer. No?
The mib2c conf file are less vital, agreed. But it's not true that comment changes are fair game. What I'd suggested was that it would be acceptable to update *standalone* documentation right up to the last moment, but that any changes to code files should be treated with more caution. Trying to protect against a lapse in concentration (e.g. a broken comment) from screwing up a full release. So strictly speaking, *any* change to any code file within a release candidate tarball should trigger a new RC release. A full release should only be made on the basis of an "untouched" release candidate. Now I don't think that's necessary here - as you say, it was only a mib2c config template, rather than any "real" code. So I'm expecting to see the full 5.2.1 release at any moment. But that's the basic idea that I was trying to put forward last year. [ I'll respond to the MfD stuff separately ] Dave ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
