Wes Hardaker wrote: > One issue that has obviously become a problem is the deadline for > which patches can be submitted for upcoming releases. Obviously if a > patch is intended to be considered for a release and it needs the > mandatory 24 hour voting window, as described in the policy document I > wrote which is available on the web page, the latest a patch should be > submitted for consideration would be 24 hours *prior* to the release > time. I'm equally as guilty at abusing this schedule, so from now on > I'll be calling out a more defined time closure window for submitting > patches for consideration starting with rc2 and beyond.
Wouldn't this also call for a more defined point in time for the actual releases? :-P Seriously, you've been calling for opinions on when to release rc1 within the Oct 27-29 time frame but didn't follow up on it before late Monday (early Tuesday for me), even though you *did* receive some feedback. This makes it hard to plan how/when to steal time from real life to improve the to-be-released code. If we're able to define definite release dates and patch closure windows in the RC phase, then that's just fine and I'm happy to agree with your policy. But if we're not (which wouldn't be surprising for a volunteer project like ours), I'd still prefer to handle this with the current flexibility rather than an additional straightjacket. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
