On 10 May 2011 13:25, Niels Baggesen <[email protected]> wrote: > Indeed, it is the very last moment to get a fix rolling. It is still > 15 days to release of Fedora 15. > > I would say that we need to revert it and make a point release of 5.6.1.1
I'm no expert on the Fedora release process, but I'd be amazed if we could get anything into Fedora 15 now. According to the release schedule (http://fedoraproject.org/wiki/Releases/15/Schedule), the Final Change deadline was yesterday. I can't really see this as being accepted as a "blocking bug", or even as a "nice to have" bug (see http://fedoraproject.org/wiki/QA:SOP_nth_bug_process) so the best we could hope for would be a "zero day" update We also need to bear in mind that 5.6.1 has been out for several months now. So we don't really know how far this change might already have been spread. A quick search shows that OpenBSD ports (at the very least) has already picked up this version. Like it or not, we've got a issue with backward compatability already. The real question here is what is the least worst way forward. Either reverting to u_long (and dealing with a somewhat confusing "window of brokenness"), or leaving things as they are (and accepting the implications for backwards compatability). Dave ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
