[development] keeping an eye on old versions

Fernando Silva fsilva.pt at gmail.com
Thu Oct 19 08:43:30 UTC 2006

I think that there is no policy!

The ideal would be the availabity of one person responsable for each release
when a new one goes out. That person would maintain the release, applying
patches or backports.

The problem is that no one wants to maintain old releases (we should
maintain the last 3 releases), and the persons who want to maintain old
releases are not *senior* enough to make critical decisions.

  Fernando Silva

On 10/19/06, Robert Garrigós Castro <robert at garrigos.cat> wrote:
>  How do we keep an eye on old versions of Drupal? What's the policy on
> this, if any?
> I'm asking this because I posted a patch for 4.6.9 (
> http://drupal.org/node/21568) which I believe it would have been nice to
> have on 4.6.10, just released. It might not be ready to apply (I believe
> it is) but then someone had had to change it's state. By the way, this is
> the only one critical bug for 4.6.9 (I believe it is critical because it
> can brake your site in some cases - http://drupal.org/node/39710)
> I know all our efforts are concentrated on drupal 5.0 but I guess there
> are many people out there using old versions (and many clients of us). I'm
> not criticising any one suposed to do this job, don't get me wrong. I just
> want to know if there is any policy and, if possible, how can we improve it.
> I might volunteer to do a regular search on critical bugs for old versions
> (actually that's easy with a feed) , revise them, and let whoever is in
> charge know about them _before_ any new minor release.
> --
> Robert Garrigós
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20061019/65d7f356/attachment.htm 

More information about the development mailing list