On 5 October 2010 23:35, Wes Hardaker <harda...@users.sourceforge.net> wrote:
> I don't think doing another rc release is worth it, even though the ipv6
> change seems semi-scary. I don't think we'll get more feedback about it
> after the fact, so I'd rather do a full release tomorrow...
> Thoughts?
I suspect that you're right about the lack of feedback.
It's certainly something that I noticed with the previous
releases that I managed.
I'm not entirely comfortable with the idea of moving straight
to final release following Niels' configure patch. I had rather
assumed this would trigger another RC version.. But I'm not
currently in a position to shoulder much if any of the burden
of RC testing, so I'm certainly not going to insist on this.
Two more general thoughts:
- We were talking about having some form of (optional)
automatic build report emailed to us, so that we could
get some feel for how widely tested things had been.
Did anything ever come of this?
- The guidelines for what should/shouldn't go into RC
feel to be being honoured as much in the breach as in
the observance. It might be worth taking another
look at the current release policy, and decide whether
it still meets our needs - or whether it needs revision
to bring it closer to actual (or desired) practise
Dave
------------------------------------------------------------------------------
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
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
