>>>>> On Wed, 6 Oct 2010 09:07:56 +0100, Dave Shield >>>>> <[email protected]> said:
DS> - We were talking about having some form of (optional) DS> automatic build report emailed to us, so that we could DS> get some feel for how widely tested things had been. DS> Did anything ever come of this? No, not yet. And it's to late to start on it for 5.6, unfortunately. DS> - The guidelines for what should/shouldn't go into RC DS> feel to be being honoured as much in the breach as in DS> the observance. It might be worth taking another DS> look at the current release policy, and decide whether DS> it still meets our needs - or whether it needs revision DS> to bring it closer to actual (or desired) practise That may be true too, and is a good topic for an admin meeting. However, we have been following the real meat of it: we have to get people to agree on applying changes. We've followed that very will this time. The problem is we need to stop voting positively on changes if we want the release out the door, or to feel comfortable with the changes to let the release go forward anyway. In this case, the change to configure *only* affects people that have tried to enable v6. And without it they actually won't get what they asked for. And if it fails to compile because of broken v6, then they need to turn off the enable switch. (the whole section of code is within 'test "x$enable_ipv6" = "xyes"') -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
