Dave Shield wrote:
That sounds a sensible timescale.
What about the 5.2.x line?
The last "real" release of that code was back in January.
(OK, we released 5.2.1.2 in June, but that wasn't a proper
release in quite the same way).
The easiest approach would probably to blitz the bug database
for both 5.2.x and the main development line in parallel,
and run the two release cycles more-or-less together.
Does that sound sensible?
Yes, 5.2.2 is overdue.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
