Hello world, it is almost two weeks since we froze Drupal 5.0.0 so I figured I'd give a quick status update. So far, only 17 modules have .info files: audio autologout contact_list countdowntimer decisions devel ecommerce google_analytics image nodewords s5 scheduler simpletest systeminfo taxonomy_access views xbview We'll want to increase that number so people can test the first beta of Drupal 5.0.0 when it hits the streets. I think we should aim to release a first beta directly after DrupalCon (or maybe even at DrupalCon). I'm thinking we're almost ready to commit the new core theme so let's get that in before we roll the first beta. -- Dries Buytaert :: http://www.buytaert.net/
On Sep 14, 2006, at 1:07 AM, Dries Buytaert wrote:
So far, only 17 modules have .info files: ... We'll want to increase that number so people can test the first beta of Drupal 5.0.0 when it hits the streets. I think we should aim to release a first beta directly after DrupalCon (or maybe even at DrupalCon).
it seems that we customarily run the betas of new releases on d.o itself. however, i think i'm going to be in the critical path for this: 1) d.o can't upgrade until project.module and friends are ported. 2) the new release system is my top priority, even ahead of porting project et al. the sooner the release system is done, the easier we'll be able to manage porting the mass of contrib to 5.0.0. i can't promise i'll have the new system done (at least the foundation of it, certainly not all the features that can be built on top of it) *and* the entire project suite of modules ported by drupalcon. if that was all i had to work on, and i *really* busted by ass, i could maybe deliver either one of those things, but certainly not both. and, right before drupalcon i'll be at another conference, giving another talk, so i'll be at least partially pre- occupied with my "real" job for the next week. ;) so, if my assumption that we'd like to upgrade d.o to the beta before/ when we release it is correct, i have serious concerns about meeting this schedule unless either i get a *lot* of help (with the upgrades, the release system, or both) or, i put the new release system on hold. however, i've got a ton of momentum now (see http://drupal.org/ node/83339 and http://drupal.org/node/83332), and i'd *love* to have the basic foundation of that in place as early in the porting-to-5.0 season as possible. just wanted to warn everyone about this reality, and call (loudly) for help in project-land if folks are serious about running 5.0.0- beta1 on d.o in a little over a week. thanks, -derek
On 14 Sep 2006, at 11:56, Derek Wright wrote:
i can't promise i'll have the new system done (at least the foundation of it, certainly not all the features that can be built on top of it) *and* the entire project suite of modules ported by drupalcon. if that was all i had to work on, and i *really* busted by ass, i could maybe deliver either one of those things, but certainly not both. and, right before drupalcon i'll be at another conference, giving another talk, so i'll be at least partially pre- occupied with my "real" job for the next week. ;)
We do want to run a beta on Drupal.org, but not necessarily the first beta. In other words, we can hold of the Drupal.org upgrade for another month or so. (We also have a dependency on simplenews.module.) Let's try to get some project module work done at DrupalCon. ;-) -- Dries Buytaert :: http://www.buytaert.net/
On Sep 14, 2006, at 5:21 AM, Dries Buytaert wrote:
We do want to run a beta on Drupal.org, but not necessarily the first beta. In other words, we can hold of the Drupal.org upgrade for another month or so. (We also have a dependency on simplenews.module.)
great. ;) i just didn't want anyone pissed off at me for holding up something important because i was working on something else that i thought was more important... glad this won't be a problem.
Let's try to get some project module work done at DrupalCon. ;-)
you know it! On Sep 14, 2006, at 7:51 AM, Dries Buytaert wrote:
There is now: DRUPAL-5-0. :)
i think larry was talking about such a branch existing on core, so us contrib maintainers have a little bit more assurance that the-moving- target-known-as-HEAD has settled down enough that it's worth the trouble to start porting. that's definitely part of why i'm not touching my modules, yet. the fact that early adopters *can* branch their module for 5.0 is nice, but simply allowing the branch name isn't the only issue here. yes, we're now in a "code freeze", but a lot can still happen that might break our contribs... ;) -derek
On Thu, September 14, 2006 11:32 am, Derek Wright said:
On Sep 14, 2006, at 7:51 AM, Dries Buytaert wrote:
There is now: DRUPAL-5-0. :)
i think larry was talking about such a branch existing on core, so us contrib maintainers have a little bit more assurance that the-moving- target-known-as-HEAD has settled down enough that it's worth the trouble to start porting. that's definitely part of why i'm not touching my modules, yet. the fact that early adopters *can* branch their module for 5.0 is nice, but simply allowing the branch name isn't the only issue here. yes, we're now in a "code freeze", but a lot can still happen that might break our contribs... ;)
-derek
No, actually I was talking about something available for contrib authors to tag/branch their code as, which thanks to Dries we now have. Yay! Having what-will-be-Drupal-5.0 settle down a bit helps as well, I agree, but having a branch for contribs helps (a) encourage people to use it and (b) helps avoid the "so what IS the status of the CVS tarball?" problem I've been talking about since yesterday. --Larry Garfield
Derek Wright wrote:
On Sep 14, 2006, at 1:07 AM, Dries Buytaert wrote:
So far, only 17 modules have .info files: ... We'll want to increase that number so people can test the first beta of Drupal 5.0.0 when it hits the streets. I think we should aim to release a first beta directly after DrupalCon (or maybe even at DrupalCon).
it seems that we customarily run the betas of new releases on d.o itself.
Not quite true. We used to run HEAD on drupal.org. This stopped about the same time last year. We only updated drupal.org in March to what is now the 4.7 branch.
however, i think i'm going to be in the critical path for this:
1) d.o can't upgrade until project.module and friends are ported.
Yes, this is always the case.
2) the new release system is my top priority, even ahead of porting project et al. the sooner the release system is done, the easier we'll be able to manage porting the mass of contrib to 5.0.0.
i can't promise i'll have the new system done (at least the foundation of it, certainly not all the features that can be built on top of it) *and* the entire project suite of modules ported by drupalcon.
There's no reason to hurry. Cheers, Gerhard
On Thu, September 14, 2006 3:07 am, Dries Buytaert said:
Hello world,
it is almost two weeks since we froze Drupal 5.0.0 so I figured I'd give a quick status update.
So far, only 17 modules have .info files:
We'll want to increase that number so people can test the first beta of Drupal 5.0.0 when it hits the streets. I think we should aim to release a first beta directly after DrupalCon (or maybe even at DrupalCon).
I'm thinking we're almost ready to commit the new core theme so let's get that in before we roll the first beta.
Is there a Drupal-5-0 tag yet? I've not started converting anything as I didn't want to have an unknown HEAD status on my modules. I was waiting for the 5.0 CVS tag (as well as some dependant modules that I know are going to take a whlie). --Larry Garfield
Is there a Drupal-5-0 tag yet? I've not started converting anything as I didn't want to have an unknown HEAD status on my modules. I was waiting for the 5.0 CVS tag (as well as some dependant modules that I know are going to take a whlie).
There is now: DRUPAL-5-0. :) -- Dries Buytaert :: http://www.buytaert.net/
participants (4)
-
Derek Wright -
Dries Buytaert -
Gerhard Killesreiter -
Larry Garfield