On Sun, Mar 13, 2016 at 08:31:04PM +0000, Mark Atwood wrote: > Hi! > > One of the policy mistakes that was killing MySQL 5.0, back in the day, is > that they would not make a point release until a target feature for that > point release was done. This was killing them/us, because of the standard > difficulties with estimation was causing every announcement to just be the > announcement of a delay, while users were waiting for bug fixes and for > proof of momentum. > > Solaris and OpenSolaris had a different philosophy: they released > regularly, metronomically, by a schedule. Features that were not ready > "missed the train", but could catch the next one. Users got their regular > bug fixes, and each announcement was positive. > > I propose that we move to a scheduled release model, with the addition of > security fast releases. > > I'm thinking every two weeks, on Tuesday morning. > > Discussion? Comments? Objections?
As someone from a distribution, I'm wondering if you'll have stable release that you'll support with at least security fixes and possibly bug fixes, and how long you think you'll support those releases. Kurt _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
