On Monday 23 July 2007, Neil Drumm wrote:
As far as I know, we don't have any precedent for doing a release candidate on a stable branch; this would be a new policy and the release infrastructure might not be set up to handle it.
We can not control the release schedule of security issues, Drupal gets released as soon as a satisfactory fix is well-tested by the security team, the stable branches could already be considered release candidates. The current 5.x will get released when needed.
I am not aware of any modules breaking in 5.x, other than this issue Darren Oh has raised.
I think the question is the definition of "when needed". There's no major security hole that needs plugging AFAIK, which is the usual impetus, but does "a crap load of bug fixes" count as "needed"? Personally I'd say yes, especially as some of those enable functionality (e.g., fixing a form submit handler so that it plays nice with overrides). If people are running 5.x-dev in production without problems now that sounds like acceptable regression testing. It's been six months. That's an eternity in Drupalcom. :-) (I'd actually support maintenance releases on a schedule, and it would make my boss the business nut happier, too.) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson