Drupal 6 beta 1 planned for next Monday

[Gábor Hojtsy-2]

Hello World!

After some short discussion with Dries, I'd like to let you know, that
I plan to release a beta 1 on next Monday (that is 3rd, September), or
very close to that. This should help us either get a second beta or an
RC by the time for DrupalCon, but this definitely depends on *you*. In
the past weeks, the RTBC queue was 4-8 patches long, and there were
important patches committed, like the update.php fixups.

If you are interested in having a Drupal 6 release sooner then later,
then please help concentrate on fixing bugs, review existing patches,
move the ones which are ready to the RTBC state. If you think that
there are definitely important issues, which might not be possible to
fix after the beta is released (ie. because they involve at least
small bits of database or API modifications), then please let me know
the issue links. If you'd like to drum up interest/reviewers for the
issues, then post them here in public, otherwise send them my way. If
anyone sees show stoppers, don't hesitate to tell.

It would also be helpful, if someone would be able to collect a list
of new features and cool modifications for a beta release post on the
frontpage. The changelog is a good start/reference. We should make
more people excited about this beta (because it is awesome :), so we
get more feedback, and a more stable release at the end. No patching
knowledge required, to write this up :)

Thanks to everyone involved with stabilizing this release, your work
is highly appreciated!

Gabor

[Yves CHEDEMOIS-2]

Gábor Hojtsy a écrit :
> If you think that
> there are definitely important issues, which might not be possible to
> fix after the beta is released (ie. because they involve at least
> small bits of database or API modifications), then please let me know
> the issue links.
>  
"Node_access_rebuild in a batch" - http://drupal.org/node/144337 needs
someone to push the RTBC button.
> It would also be helpful, if someone would be able to collect a list
> of new features and cool modifications for a beta release post on the
> frontpage. The changelog is a good start/reference. We should make
> more people excited about this beta (because it is awesome :), so we
> get more feedback, and a more stable release at the end. No patching
> knowledge required, to write this up :)
>  
I don't think the node cache patch got an entry in Changelog ?

Yves

[Jeff Eaton]

On Aug 28, 2007, at 5:15 PM, Yves Chedemois wrote:

> I don't think the node cache patch got an entry in Changelog ?

I'm still VERY concerned about the node caching patch. It seems like  
*exactly* the sort of thing that should never go in after a code  
freeze. It has the potential to introduce baffling and obscure bugs  
in existing modules -- poll.module was hit, for example -- after the  
point that we told people they were safe in porting things to D6.

--Jeff

[Steven Peck-2]

I did some preliminary posting on the changelog a short time ago and
issue's associated which can help with such a writeup.
http://www.blkmtn.org/drupal6-changelog

I will note, this weekend is a USA holiday (Sat-Mon) so people may be scarce.

-sp

On 8/28/07, Gábor Hojtsy <gabor@...> wrote:

> Hello World!
>
> After some short discussion with Dries, I'd like to let you know, that
> I plan to release a beta 1 on next Monday (that is 3rd, September), or
> very close to that. This should help us either get a second beta or an
> RC by the time for DrupalCon, but this definitely depends on *you*. In
> the past weeks, the RTBC queue was 4-8 patches long, and there were
> important patches committed, like the update.php fixups.
>
> If you are interested in having a Drupal 6 release sooner then later,
> then please help concentrate on fixing bugs, review existing patches,
> move the ones which are ready to the RTBC state. If you think that
> there are definitely important issues, which might not be possible to
> fix after the beta is released (ie. because they involve at least
> small bits of database or API modifications), then please let me know
> the issue links. If you'd like to drum up interest/reviewers for the
> issues, then post them here in public, otherwise send them my way. If
> anyone sees show stoppers, don't hesitate to tell.
>
> It would also be helpful, if someone would be able to collect a list
> of new features and cool modifications for a beta release post on the
> frontpage. The changelog is a good start/reference. We should make
> more people excited about this beta (because it is awesome :), so we
> get more feedback, and a more stable release at the end. No patching
> knowledge required, to write this up :)
>
> Thanks to everyone involved with stabilizing this release, your work
> is highly appreciated!
>
> Gabor
>

[Peter Wolanin]

Hi Gábor,

a minor thing, but some version of this patch should go in:

Menu system fix- setting the active path
http://drupal.org/node/148677

since right now menu_set_active_item() does nothing at all.  Or
alternately, that function should be removed completely.

-Peter

On 8/28/07, Gábor Hojtsy <gabor@...> wrote:

> Hello World!
>
> After some short discussion with Dries, I'd like to let you know, that
> I plan to release a beta 1 on next Monday (that is 3rd, September), or
> very close to that. This should help us either get a second beta or an
> RC by the time for DrupalCon, but this definitely depends on *you*. In
> the past weeks, the RTBC queue was 4-8 patches long, and there were
> important patches committed, like the update.php fixups.
>
> If you are interested in having a Drupal 6 release sooner then later,
> then please help concentrate on fixing bugs, review existing patches,
> move the ones which are ready to the RTBC state. If you think that
> there are definitely important issues, which might not be possible to
> fix after the beta is released (ie. because they involve at least
> small bits of database or API modifications), then please let me know
> the issue links. If you'd like to drum up interest/reviewers for the
> issues, then post them here in public, otherwise send them my way. If
> anyone sees show stoppers, don't hesitate to tell.
>
> It would also be helpful, if someone would be able to collect a list
> of new features and cool modifications for a beta release post on the
> frontpage. The changelog is a good start/reference. We should make
> more people excited about this beta (because it is awesome :), so we
> get more feedback, and a more stable release at the end. No patching
> knowledge required, to write this up :)
>
> Thanks to everyone involved with stabilizing this release, your work
> is highly appreciated!
>
> Gabor
>

[Larry Garfield]

Removing it would be a somewhat serious regression, so I would prefer making
it work to removing it. :-)

On Tuesday 28 August 2007, Peter Wolanin wrote:

> Hi Gábor,
>
> a minor thing, but some version of this patch should go in:
>
> Menu system fix- setting the active path
> http://drupal.org/node/148677
>
> since right now menu_set_active_item() does nothing at all.  Or
> alternately, that function should be removed completely.
>
> -Peter

--
Larry Garfield AIM: LOLG42
larry@... 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

[Karoly Negyesi]

> I'm still VERY concerned about the node caching patch. It seems like  
> *exactly* the sort of thing that should never go in after a code  
> freeze.

Then unroll it. My work is worthless anyways apparently. After pouring unbelievable amount of time into a patch in a very short time, instead of meaningful reviews I get a report about a surplus space. Congratulations.

[Gábor Hojtsy-2]

Could you list some modules which are getting buggy with this feature
in Drupal 6? What you say is very much floating in the air now without
actual examples. Poll module was there, and easily fixed.

Gabor

On 8/29/07, Jeff Eaton <jeff@...> wrote:

>
> On Aug 28, 2007, at 5:15 PM, Yves Chedemois wrote:
>
> > I don't think the node cache patch got an entry in Changelog ?
>
> I'm still VERY concerned about the node caching patch. It seems like
> *exactly* the sort of thing that should never go in after a code
> freeze. It has the potential to introduce baffling and obscure bugs
> in existing modules -- poll.module was hit, for example -- after the
> point that we told people they were safe in porting things to D6.
>
> --Jeff
>

[Angela Byron-3]

> If you think that
> there are definitely important issues, which might not be possible to
> fix after the beta is released (ie. because they involve at least
> small bits of database or API modifications), then please let me know
> the issue links.

Here's my sense from glancing through the first couple pages of the  
critical queue:

API changes that need a firm yes/no before beta:
- Missing feature from schema API: load/save records : http://
drupal.org/node/169982
- actions.inc is always included, but breaks without actions.module:  
http://drupal.org/node/155828
- jQuery 1.1.4: http://drupal.org/node/170224

*Really* Critical bug fixes (we would actually do more harm to the  
project than good shipping a beta without these fixed, imo):
- Menu update from D5 -> D6 : http://drupal.org/node/147657 (duh :P)
- jQuery interaction with Garland breaks modules page: http://
drupal.org/node/134307 -- modules page totally unusable in Safari
- First user installed as uid = 2 in MySQL 4.1: http://drupal.org/ 
node/149540 - will prevent user from administering the site if  
they're bitten by this bug, which appears on RHEL 4 and other distros.

I will try and give it a typical 'webchick' touch over the weekend  
and update with any other critical issues (hopefully can work on  
fixing some of them too).

-Angie

[Angela Byron-3]

On 29-Aug-07, at 11:46 AM, Angela Byron wrote:

> *Really* Critical bug fixes (we would actually do more harm to the  
> project than good shipping a beta without these fixed, imo):

Here's another nasty one that I forgot about:

upload module deletes files on submission: http://drupal.org/node/168813

[Earl Miles]

Gábor Hojtsy wrote:
> Could you list some modules which are getting buggy with this feature
> in Drupal 6? What you say is very much floating in the air now without
> actual examples. Poll module was there, and easily fixed.

I'm not sure I'd agree with the 'easily' part. It was fixed (though that
fix has not yet been committed) but I had to be a little creative.

[Angela Byron-3]

On 29-Aug-07, at 4:19 PM, Angela Byron wrote:

>
> On 29-Aug-07, at 11:46 AM, Angela Byron wrote:
>
>> *Really* Critical bug fixes (we would actually do more harm to the  
>> project than good shipping a beta without these fixed, imo):
>
> Here's another nasty one that I forgot about:
>
> upload module deletes files on submission: http://drupal.org/node/ 
> 168813

And another:

http://drupal.org/node/151394 : Kills Drupal with a fatal error if  
settings.php is messed up in any way. It's RTBCed already though, so  
hopefully can get in quickly.

I will have more time to spend on this this weekend where I can  
compile a big list of these rather than mailing the one-off ones that  
bubble up. Sorry for the noise. :( I'd e-mail Gabor separately, but  
it also seems like it'd be good for all of us to have a sense of  
where the priorities should be.

-Angie

[Gábor Hojtsy-2]

On 8/28/07, Gábor Hojtsy <gabor@...> wrote:
> Hello World!
>
> After some short discussion with Dries, I'd like to let you know, that
> I plan to release a beta 1 on next Monday (that is 3rd, September), or
> very close to that.

Seems like we could only make the "very close to that" or a "close to
that". You guys did a great job in the last few days to uncover bugs
and provide fixes. We managed to handle the RTBC queue with Dries, but
it is already the middle of the afternoon Monday (Central European
Time), and there are still more beta stopper bugs left. So we need to
postpone the first beta with two or three days, to have time to
properly review all the fixes. In the meantime, do not hesitate to
submit more fixes, and especially to review existing ones.

Thanks for the effort of all parties involved,
Gabor

[Karoly Negyesi]

> and provide fixes. We managed to handle the RTBC queue with Dries, but
> it is already the middle of the afternoon Monday (Central European
> Time), and there are still more beta stopper bugs left.

But they are all patched up. It's fairly common to release around 7-8pm CET -- please reconsider. I know, I know nothing urgent and we release when it's ready -- but it is .

[Gábor Hojtsy-2]

You know, some people have personal duties. I am not even at my
computer today and tomorrow (just checked in for ten minutes to see
whether there are any seriously urgent things to do). I also contacted
Dries to take on the beta, but he is very busy with some phd related
deadlines. Thankfully this short extra delay makes the first beta even
better

Gabor

On 9/3/07, Karoly Negyesi <karoly@...> wrote:
> > and provide fixes. We managed to handle the RTBC queue with Dries, but
> > it is already the middle of the afternoon Monday (Central European
> > Time), and there are still more beta stopper bugs left.
>
> But they are all patched up. It's fairly common to release around 7-8pm CET -- please reconsider. I know, I know nothing urgent and we release when it's ready -- but it is .
>

[Karoly Negyesi]

> Thankfully this short extra delay makes the first beta even better

You are right of course and that's why you are the Drupal 6 maintainer. I am just patching what the others find and wow there were some findings late yesterday (see forum module shadow copy and 'user' throwing 403)