[development] Drupal 5 incremental release?

Neil Drumm drumm at delocalizedham.com
Mon Jul 23 21:57:58 UTC 2007

On 7/23/07, Adrian Simmons <adrinux at perlucida.com> wrote:
> Earnie Boyd wrote:
>  > For a module to break merely because of an incremental upgrade
> > seems a bit over anxious to include new functionality in core.
> Sometimes it's been necessary (or at least pragmatic) to change an API to
> fix a bug, usually security related. That's all that's been said.
> Personally I'm running 5.x-dev because of bugs in 5.1...
> As for an update breaking contrib modules - isn't that why we have release
> candidates? I know normally those are reserved for major releases, but in
> this case might it not be wise to have a 5.2-RC ?

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.

Neil Drumm

More information about the development mailing list