On Tue, 2005-10-18 at 10:44 +0200, Thomas Anders wrote: > Do we agree that documentation/example updates do not > fall under these rules and can go in immediately?
Standalone documentation updates can go in right up to the last minute. Documentation embedded within code files should be OK up until the final RC tarball, but shouldn't be changed between that and full release. The aim is that the final RC tarball should be re-used as the final release version - basically unchanged (apart from automatic update of version numbers). Updating embedded documentation opens up the risk of breaking the code (e.g. due to a corrupted comment). It's a relatively small risk, so such changes are OK during the RC phase. But it's not worth taking this right to the wire. I'd suggest that the same approach can probably be taken to updating example code - particularly assuming that they're not included in a default build. Bottom line - how much damage would be done if you screwed up editing each particular file? The more damage, the less acceptable it is to change it late on. Make sense? Dave ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
