|
List Info
Thread: gearing up for a 6.0 RC4
|
|
| gearing up for a 6.0 RC4 |
|
2008-02-07 07:28:50 |
Hey,
>From the looks of the criticals queue, we need to push
out an RC4
before the final release can be rolled. We fixed several
critical
issues in the last few days, and some are still to be fixed.
The list
is not too long, so please help test patches there:
http://drupal.org/project/issues?projects=3060&
amp;categories=bug,task&priorities=1&states=1,8,
13,14&versions=97368,184399,175832,194287,198188,202820,
208616,216077
I also drafted an RC4 announcement for publication. If
someone feels
like making it better, hop to http://drupal.org/dr
upal-6.0-rc4 (only
people with permission to edit unpublished full HTML nodes
again).
Ideally, RC4 could be out in around 8-9 hours today, but the
critical
bugs will define the exact schedule. It would be great to
see a final
6.0 out early next week. Please help in the criticals queue
to make
this happen. Minor code tweaks might make the code look
better, but in
fact do not help the Drupal 6 release stabilize as much as
the same
time spent on the critical bugs.
Thanks,
Gabor
|
|
| Re: gearing up for a 6.0 RC4 |
 
United States |
2008-02-07 08:46:53 |
Gábor Hojtsy wrote:
> From the looks of the criticals queue, we need to push
out an RC4
> before the final release can be rolled. We fixed
several critical
> issues in the last few days, and some are still to be
fixed.
I'd really like to see the "pending bugs" list
reduced quite a bit before
6.0 rolls out. I don't know about anyone else, but rolling
a new version
with 82 known bugs seems a bit presumptuous to me. As a
matter of fact, I
see some on the list that I would consider more important
than "normal," if
not "critical."
Nancy E. Wichmann, PMP
|
|
| Re: gearing up for a 6.0 RC4 |
|
2008-02-07 09:05:24 |
|
On Feb 7, 2008 2:46 PM, Nancy Wichmann wrote:
I'd really like to see the "pending bugs" list reduced quite a bit before
6.0 rolls out. I don't know about anyone else, but rolling a new version
with 82 known bugs seems a bit presumptuous to me. As a matter of fact, I
see some on the list that I would consider more important than "normal," if
not "critical."
Nancy E. Wichmann, PMP
Some of those 82 pending bugs have been around since 4.7 or earlier, many of them are duplicates of other things which have already been fixed or postponed to D7, some haven't been reproduced yet. If you'd like to see that list reduced before release, the best thing to do is to dive into that queue and work out what is and isn't valid, explain steps to reproduce (many of those reports don't have any), supply a patch etc. And if you consider something critical, then mark it as such with your justifications - someone will always mark it back to 'normal' if they disagree.
Many of the patches in the 'patch queue' - currently running at 381 - are for bugs as well, so there's plenty of material to work with.
This is the first release where there's been a running count attached to the bug and patch queues (that I know of) - I'd be willing to bet that 4.7 and 5.x were released with more than there currently is against D6. There's also plenty of bugs in D5 that are dealt with in D6 but required fundamental api changes that'll never be backported. It goes both ways.
|
| Re: gearing up for a 6.0 RC4 |
|
2008-02-07 11:19:04 |
On Feb 7, 2008 4:05 PM, catch <catch56 googlemail.com> wrote:
> On Feb 7, 2008 2:46 PM, Nancy Wichmann wrote:
> > I'd really like to see the "pending
bugs" list reduced quite a bit before
> > 6.0 rolls out. I don't know about anyone else,
but rolling a new version
> > with 82 known bugs seems a bit presumptuous to me.
As a matter of fact, I
> > see some on the list that I would consider more
important than "normal,"
> > if not "critical."
>
> Many of the patches in the 'patch queue' - currently
running at 381 - are
> for bugs as well, so there's plenty of material to work
with.
>
> This is the first release where there's been a running
count attached to the
> bug and patch queues (that I know of) - I'd be willing
to bet that 4.7 and
> 5.x were released with more than there currently is
against D6. There's also
> plenty of bugs in D5 that are dealt with in D6 but
required fundamental api
> changes that'll never be backported. It goes both
ways.
Nancy, catch summarizes the situation quite accurately. All
previous
Drupal versions were released with a running number of bugs
and
pending patches. We could go on for months fixing what some
people
think are bugs, while certain "bugos" behaviors
are in the software
for years now. Even some things getting into the criticals
queue (and
then being moved to Drupal 7) are simply missing features
which people
would use naturally, and their absence looks like a critical
bug for
some.
Gabor
|
|
[1-4]
|
|