[development] Some issues and their fixes with Drupal 4.6.6 and PostgreSQL

[Khalid B]

On 4/20/06, Dries Buytaert <dries.buytaert at gmail.com> wrote:
>
> On 20 Apr 2006, at 03:11, Khalid B wrote:
> > It is unlikely that bug fixes against 4.6.x would be accepted,
> > simply because
> > we try to restrict fixes to stable releases to secruity fixes only.
>
> This information is incorrect.
>
> The Drupal 4.6 branch is being maintained and fixes are being
> committed.  (See the release announcements for details.)  We are,
> however, slightly more conservative with patches that fix bugs in
> Drupal 4.6.  Given that your patches are tested and supported by a
> number of people, they can make it into the next Drupal 4.6
> maintenance release.
>
> So best to submit your patch to the issue tracker and to rally up
> some people to thumb it up.

I was merely reiterating our historical practice to date, which is
basically what I said. See for example Dries' comment and
closing an issue as won't fix.
http://drupal.org/node/43712#comment-68805

However, this is in the past, and things have changed now. We have
two more committers to core, and people designated for specific
branches.

This means we have more capacity to maintain the previous branch
than we had before.

So, if this is a change in policy that we should consider going forward,
then that is a good thing to have. We improve things as we move forward
including policies and processes.