Hello world, I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable. Sounds good? -- Dries Buytaert :: http://www.buytaert.net/
Dries Buytaert wrote:
Hello world,
I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable.
Sounds good? Is that 4 months starting today? Or 4 months starting 2 weeks ago? ;-) The morning of June 1st as an official 'code freeze' date would be easy to mark on a calendar...
--Jeff
On 31 Jan 2007, at 22:34, Jeff Eaton wrote:
I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable.
Is that 4 months starting today? Or 4 months starting 2 weeks ago? ;-) The morning of June 1st as an official 'code freeze' date would be easy to mark on a calendar...
Let's pick June 1st then. :-) -- Dries Buytaert :: http://www.buytaert.net/
Is there a centralized place where the requirements for Drupal 6.0 are documented? Victor Kane http://awebfactory.com.ar On 1/31/07, Dries Buytaert <dries.buytaert@gmail.com> wrote:
On 31 Jan 2007, at 22:34, Jeff Eaton wrote:
I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable.
Is that 4 months starting today? Or 4 months starting 2 weeks ago? ;-) The morning of June 1st as an official 'code freeze' date would be easy to mark on a calendar...
Let's pick June 1st then. :-)
-- Dries Buytaert :: http://www.buytaert.net/
On 31 Jan 2007, at 22:34, Jeff Eaton wrote:
Dries Buytaert wrote:
Hello world,
I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable.
Sounds good?
Is that 4 months starting today? Or 4 months starting 2 weeks ago? ;-) The morning of June 1st as an official 'code freeze' date would be easy to mark on a calendar...
Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-) -- Dries Buytaert :: http://www.buytaert.net/
On 31 Jan 2007, at 22:55, Stefan Borchert wrote:
Dries Buytaert schrieb:
Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-) But it already 2007 :-{ Drats. Missed opportunity. ;-)
-- Dries Buytaert :: http://www.buytaert.net/
On 1/31/07 4:58 PM, Dries Buytaert wrote:
On 31 Jan 2007, at 22:55, Stefan Borchert wrote:
Dries Buytaert schrieb:
Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-) But it already 2007 :-{ Drats. Missed opportunity. ;-)
Darn that 4.7! -- James Walker :: http://walkah.net/ :: xmpp:walkah@walkah.net
On 1/31/07, Dries Buytaert <dries.buytaert@gmail.com> wrote:
On 31 Jan 2007, at 22:55, Stefan Borchert wrote:
Dries Buytaert schrieb:
Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-) But it already 2007 :-{ Drats. Missed opportunity. ;-)
There is always 07/07/07. Would be better as a release date, not a freeze date.
Dries Buytaert schrieb: Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-) But it already 2007 :-{ Drats. Missed opportunity. ;-)
There is always 07/07/07.
Since we like playing with dates (yes, a bit off topic this sorry) who on the list knows where they were for these two "moments" in history:- 01:23:45 6/7/89 12:34:56 7/8/90 Sadly, yes I do know, precisely, where and when I was ;) regards, --Andy (AjK)
Sadly, yes I do know, precisely, where and when I was ;)
It's very interesting how people think this "people know where they were and what they did at a certain important date" is scientific research. In fact, it's not, the meme was introduced by Frederick Forsyth's Odessa file and it really spread. People were interviewed just after the Challenger catastrophe and 9/11 and checked later -- and what they remembered actually rarely matched. Regards, NK
On 1/31/07 8:45 PM, Khalid B wrote:
On 1/31/07, *Dries Buytaert* <dries.buytaert@gmail.com <mailto:dries.buytaert@gmail.com>> wrote:
On 31 Jan 2007, at 22:55, Stefan Borchert wrote:
> Dries Buytaert schrieb: >> Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-) > But it already 2007 :-{ Drats. Missed opportunity. ;-)
There is always 07/07/07.
I was *almost* born on 7/7/77 ... incidentally, I think we should release d6 on my 30th birthday (7/10/07). Y'know... 'cause I'm special ;) -- James Walker :: http://walkah.net/ :: xmpp:walkah@walkah.net
On 1/31/07, James Walker <walkah@walkah.net> wrote:
On 1/31/07 8:45 PM, Khalid B wrote:
On 1/31/07, *Dries Buytaert* <dries.buytaert@gmail.com <mailto:dries.buytaert@gmail.com>> wrote:
On 31 Jan 2007, at 22:55, Stefan Borchert wrote:
> Dries Buytaert schrieb: >> Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-) > But it already 2007 :-{ Drats. Missed opportunity. ;-)
There is always 07/07/07.
I was *almost* born on 7/7/77 ... incidentally, I think we should release d6 on my 30th birthday (7/10/07). Y'know... 'cause I'm special ;)
Born in 1977? Dries, why are you letting kids come in here and ... Oh, wait ... --
James Walker :: http://walkah.net/ :: xmpp:walkah@walkah.net
Stefan Borchert wrote:
Dries Buytaert schrieb:
Or we could freeze D6 on 6/6/6 instead of 1/6/6. :-)
But it already 2007 :-{ It is a new twist in European date formatting that went into law on 1 Jan, 07. The year is now officially always off by one.
Dries Buytaert wrote:
Hello world,
I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable.
Sounds good?
-- Dries Buytaert :: http://www.buytaert.net/
I am a developer who considers himself to be at ease with Drupal, but far from being an Drupal expert. Drupal is my main development platform, and probably as many of you do, I also dream Drupal sometimes :-) With regards to that - I feel that from 4.7 to 5 Drupal changed in such a extreme manner, that it will take most of the developers 4 months only to get to know Drupal 5 properly... Most of Drupal developers are not core developers, and might be intimidated by rapid, extreme changes. I'm talking about API, not, for example, the CCK integration. Drupal is already reputated to have a slow learning curve, and every time you get to the summit, the mountain becomes higher :-) I can see the need to release a newer, better CMS when possible, certainly in a very competitive surrounding, and maybe that's the right thing to do, ideally. BUT (and here comes the "but"), don't we risk being a bit too fast? The intuitive answer is "No, we found a better way to do things, so why wait?!". I see it a bit like raising a child. You can't always tell him/her "that's a better way, do like this". They need time to assimilate and absorb. It's healthier for them and their growth would be much more stable. The same might be applicable to software. And I could easily find an example from climbing too fast and running out of oxygen, or from any other fields of interest you may have, just for the sake of making things clearer. It's not about not wanting to be higher, but it's about doing things the right way. I don't know... maybe I'm just getting too old and slow... Finally, and this relates to a parallel discussion about maintaining "old" modules, we must remember that our clients (we do work for them, eventually), can not all afford upgrades so often. This might sound idiotic, but it must be taken into consideration. Smart clients, and most of them are, are studying the market well before investing in such a content platform, that is becoming more and more centric in business. If we move too fast for modules' maintainers to upgrade their modules, we'll end up with a very advanced CMS, but our sites won't survive more than a year. OK - while writing this I already received two excited mails about the date (Dries is a year behind, go to sleep... or wake up! ;-) ), and anyway, I'm reaching the midnight barrier where I'm at (remember - no posts to the list after midnight for the sake of our sanity :-) ), and I wrote too much (maybe I AM becoming too old....), So I'll just finish with a small proposition: let's try to at least make n effort and prepare the community for the changes. Periodic posts about tendencies in the development will soften the shock when D6 lands here. Good night all, Zohar
Zohar Stolar wrote:
Dries Buytaert wrote:
Hello world,
I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable.
Sounds good?
-- Dries Buytaert :: http://www.buytaert.net/
I am a developer who considers himself to be at ease with Drupal, but far from being an Drupal expert. Drupal is my main development platform, and probably as many of you do, I also dream Drupal sometimes :-) With regards to that - I feel that from 4.7 to 5 Drupal changed in such a extreme manner, that it will take most of the developers 4 months only to get to know Drupal 5 properly... Most of Drupal developers are not core developers, and might be intimidated by rapid, extreme changes. I'm talking about API, not, for
Please stop right there. We've had that discussion often enough, please consult the archives. Cheers, Gerhard
On Jan 31, 2007, at 3:03 PM, Zohar Stolar wrote:
With regards to that - I feel that from 4.7 to 5 Drupal changed in such a extreme manner, that it will take most of the developers 4 months only to get to know Drupal 5 properly... Most of Drupal developers are not core developers, and might be intimidated by rapid, extreme changes. I'm talking about API, not, for example, the CCK integration. Drupal is already reputated to have a slow learning curve, and every time you get to the summit, the mountain becomes higher :-)
I can see the need to release a newer, better CMS when possible, certainly in a very competitive surrounding, and maybe that's the right thing to do, ideally. BUT (and here comes the "but"), don't we risk being a bit too fast?
As a Drupal enthusiast since Drupal 4.4 days, I can say that I'm delighted and relieved that Drupal is evolving so fast. I remember when 4.5 was the bee's knees. Then it was just awful compared with 4.6, which was just not good enough once 4.7 came out.... I'm not so sure the world is flat, but time stands still for no one, and the web is developing at such a rapid rate that it behooves the Drupal community to continue to not only keep apace but even set the pace. Each major release has involved a major learning curve, yes, but this amounts to learning one's way around a better cms. I wouldn't go backwards on a bet. I believe your concern about clients who are happy with their existing sites is well placed. However, I would suggest that this is more on the matter of maintaining support for older systems, and not a matter of how rapidly the newest and bestest stuff rolls out. June 1 -- that's not even summer! That is fabulous! Laura
Laura Scott wrote:
I'm not so sure the world is flat, but time stands still for no one, and the web is developing at such a rapid rate that it behooves the Drupal community to continue to not only keep apace but even set the pace. So absolutely right! Everybody fasten your seat belts... we've picked up some crazy smart people who are contributing to core, and the Drupal of today is the poormansdrupal of tomorrow. Hit the gas pedal and enjoy the ride =)
Laura Scott wrote:
I'm not so sure the world is flat, but time stands still for no one, and the web is developing at such a rapid rate that it behooves the Drupal community to continue to not only keep apace but even set the pace.
Each major release has involved a major learning curve, yes, but this amounts to learning one's way around a better cms. I wouldn't go backwards on a bet.
June 1 -- that's not even summer! That is fabulous!
Laura
Killes sent me to the archives, but you got me hooked even before I got to there! June 1st - I'll be there!
As someone who is new to Drupal (maybe I have no business giving my opinion at all, but I think it should be said in a flameless way) but not at all to software engineering, and who is just beginning to architect and author web applications based on Drupal, I would say that I denote a slight contradiction between some of the thorny issues being debated on this list (everything is a node vs. don't overload node hook system; developing an orthogonal API for the various API's, etc., etc., etc.,), and starting a code freeze in four months. I just don't see these being resolved in four months. I sort of perhaps naively assume that it would make no sense making another major release without dealing with those problems. Your damned if you do and damned if you don't: if you don't you "fall behind the web 2 race for splashiness"; if you do, you are painting yourself into a corner and risking everything drupal stands for: cleanness, well-thought out stuff, lean and mean... On the other hand, if "Drupal 6" is drupal 5 debugged and jquery up front usability gains, etc., then that is ok, would be an advance, no matter what you call it. But if the rush to freeze also freezes some stuff that depends on the thorny points in the middle of the river, so to speak, then that could cause problems. Victor Kane http://awebfactory.com.ar On 1/31/07, Laura Scott <laura@pingv.com> wrote:
On Jan 31, 2007, at 3:03 PM, Zohar Stolar wrote:
With regards to that - I feel that from 4.7 to 5 Drupal changed in such a extreme manner, that it will take most of the developers 4 months only to get to know Drupal 5 properly... Most of Drupal developers are not core developers, and might be intimidated by rapid, extreme changes. I'm talking about API, not, for example, the CCK integration. Drupal is already reputated to have a slow learning curve, and every time you get to the summit, the mountain becomes higher :-)
I can see the need to release a newer, better CMS when possible, certainly in a very competitive surrounding, and maybe that's the right thing to do, ideally. BUT (and here comes the "but"), don't we risk being a bit too fast?
As a Drupal enthusiast since Drupal 4.4 days, I can say that I'm delighted and relieved that Drupal is evolving so fast. I remember when 4.5 was the bee's knees. Then it was just awful compared with 4.6, which was just not good enough once 4.7 came out....
I'm not so sure the world is flat, but time stands still for no one, and the web is developing at such a rapid rate that it behooves the Drupal community to continue to not only keep apace but even set the pace.
Each major release has involved a major learning curve, yes, but this amounts to learning one's way around a better cms. I wouldn't go backwards on a bet.
I believe your concern about clients who are happy with their existing sites is well placed. However, I would suggest that this is more on the matter of maintaining support for older systems, and not a matter of how rapidly the newest and bestest stuff rolls out.
June 1 -- that's not even summer! That is fabulous!
Laura
On 1/31/07 5:30 PM, Victor Kane wrote:
As someone who is new to Drupal (maybe I have no business giving my opinion at all, but I think it should be said in a flameless way) but not at all to software engineering, and who is just beginning to architect and author web applications based on Drupal, I would say that I denote a slight contradiction between some of the thorny issues being debated on this list (everything is a node vs. don't overload node hook system; developing an orthogonal API for the various API's, etc., etc., etc.,), and starting a code freeze in four months. I just don't see these being resolved in four months.
I sort of perhaps naively assume that it would make no sense making another major release without dealing with those problems.
It's an interesting point. One thing to keep in mind, however, is the mental effect of having a "hard" deadline. As anyone who has been around for a few release cycles can attest - there is a disproportionate flurry of patch submissions "at the deadline". So having a "hard" deadline is largely motivational. To get people thinking & started on their "big ideas" for the next drupal. Drupal always has, and always will be 'released when ready'.
Your damned if you do and damned if you don't: if you don't you "fall behind the web 2 race for splashiness"; if you do, you are painting yourself into a corner and risking everything drupal stands for: cleanness, well-thought out stuff, lean and mean...
Well, I don't think drupal has every really aspired to being splashy... again, the release dates are more about keeping drupal moving forward than trying to keep up with or "beat" any other platform.
On the other hand, if "Drupal 6" is drupal 5 debugged and jquery up front usability gains, etc., then that is ok, would be an advance, no matter what you call it.
But if the rush to freeze also freezes some stuff that depends on the thorny points in the middle of the river, so to speak, then that could cause problems.
4 months is a *lot* of time in drupal land. Stick around :) -- James Walker :: http://walkah.net/ :: xmpp:walkah@walkah.net
On 1/31/07, James Walker <walkah@walkah.net> wrote:
On 1/31/07 5:30 PM, Victor Kane wrote:
I sort of perhaps naively assume that it would make no sense making another major release without dealing with those problems.
It's an interesting point. One thing to keep in mind, however, is the mental effect of having a "hard" deadline. As anyone who has been around for a few release cycles can attest - there is a disproportionate flurry of patch submissions "at the deadline". So having a "hard" deadline is largely motivational. To get people thinking & started on their "big ideas" for the next drupal.
Drupal always has, and always will be 'released when ready'.
That's great, I'm all for that. I am simply concerned because I don't see any correlation between announced new functionality and the estimation of four months, and even less, an iterations plan. I suppose that drupal veterans may have a clear picture, but I advise that the target functionality be gleaned from the feature request list and prioritized.
Your damned if you do and damned if you don't: if you don't you "fall behind the web 2 race for splashiness"; if you do, you are painting yourself into a corner and risking everything drupal stands for: cleanness, well-thought out stuff, lean and mean...
Well, I don't think drupal has every really aspired to being splashy... again, the release dates are more about keeping drupal moving forward than trying to keep up with or "beat" any other platform.
That's true. And I applaud it.
On the other hand, if "Drupal 6" is drupal 5 debugged and jquery up front usability gains, etc., then that is ok, would be an advance, no matter what you call it.
But if the rush to freeze also freezes some stuff that depends on the thorny points in the middle of the river, so to speak, then that could cause problems.
4 months is a *lot* of time in drupal land. Stick around :) --
cool, let's go for it! I know I will pitch in where I can!
James Walker :: http://walkah.net/ :: xmpp:walkah@walkah.net
Victor Kane wrote:
On 1/31/07, James Walker <walkah@walkah.net> wrote:
On 1/31/07 5:30 PM, Victor Kane wrote:
I sort of perhaps naively assume that it would make no sense making another major release without dealing with those problems.
It's an interesting point. One thing to keep in mind, however, is the mental effect of having a "hard" deadline. As anyone who has been around for a few release cycles can attest - there is a disproportionate flurry of patch submissions "at the deadline". So having a "hard" deadline is largely motivational. To get people thinking & started on their "big ideas" for the next drupal.
Drupal always has, and always will be 'released when ready'.
That's great, I'm all for that. I am simply concerned because I don't see any correlation between announced new functionality
Where was any new functionality announced?
and the estimation of four months, and even less, an iterations plan. I
It's open source. That doesn't exclude a plan, but in Drupal's case there really isn't one.
suppose that drupal veterans may have a clear picture, but I advise that the target functionality be gleaned from the feature request list and prioritized.
We've never cared about feature requests too. Individuals may have, but not the project as such. Cheers, Gerhard
Victor Kane wrote:
I would say that I denote a slight contradiction between some of the thorny issues being debated on this list (everything is a node vs. don't overload node hook system; developing an orthogonal API for the various API's, etc., etc., etc.,), and starting a code freeze in four months. I just don't see these being resolved in four months. Not all the theoretical debates will be resolved in 4 months. The things you just mentioned are ongoing discussions. The current changes that are happening to the menu system started off as such a debate, and got architected months ago at a conference while we were still trying to get Drupal 5 going. D6 will see its share of improvements, both on the front-end and the back-end, and it is good to have a release every year to make sure we get to a stable point (ie focus on real bug fixing). Maybe we'll get some of those issues you mentioned into D6, maybe not. Waiting too long between releases is very bad, though, because the chasm between versions becomes unmanageable.
Welcome to Drupal =)
On 1/31/07, Robert Douglass <rob@robshouse.net> wrote:
Victor Kane wrote:
I would say that I denote a slight contradiction between some of the thorny issues being debated on this list (everything is a node vs. don't overload node hook system; developing an orthogonal API for the various API's, etc., etc., etc.,), and starting a code freeze in four months. I just don't see these being resolved in four months. Not all the theoretical debates will be resolved in 4 months. The things you just mentioned are ongoing discussions. The current changes that are happening to the menu system started off as such a debate, and got architected months ago at a conference while we were still trying to get Drupal 5 going. D6 will see its share of improvements, both on the front-end and the back-end, and it is good to have a release every year to make sure we get to a stable point (ie focus on real bug fixing). Maybe we'll get some of those issues you mentioned into D6, maybe not. Waiting too long between releases is very bad, though, because the chasm between versions becomes unmanageable.
Welcome to Drupal =)
I really appreciate being filled in like this. It is clear to me from what you say that the major releases are important development iterations and that you guys have given all of this a lot of consideration. Hope I can make it to Sunnyvale in March! In any case, I am planning on putting my shoulder to the wheel as well as giving my opinion. :) I have proposed and had Drupal accepted on a couple of quite important projects, and the small team we have assigned, for example, to an educational project, will have to solve all manner of problems with Drupal 5, and there will definitely be some modules for jquery interface library, on the one hand, and access and roles stuff, on the other. So thanks, I am definitely here for the long haul. Victor Kane http://awebfactory.com.ar
On Thu, 2007-02-01 at 00:03 +0200, Zohar Stolar wrote:
Dries Buytaert wrote:
Hello world,
I'm mailing to talk a bit more about the Drupal 6 release schedule. Drupal 5 had a 3 month development period, followed by a 5 month code freeze. For Drupal 6, I'd like to propose a 4 month development period, followed by a code freeze. As with Drupal 5, the code freeze will be guaranteed to be at least 2 months to give module authors time to plan and catch up. In practice, and depending on the state of Drupal core at the code freeze date, it might take more than two months to get things stable.
Sounds good?
-- Dries Buytaert :: http://www.buytaert.net/
I am a developer who considers himself to be at ease with Drupal, but far from being an Drupal expert. Drupal is my main development platform, and probably as many of you do, I also dream Drupal sometimes :-) With regards to that - I feel that from 4.7 to 5 Drupal changed in such a extreme manner, that it will take most of the developers 4 months only to get to know Drupal 5 properly...
I've accepted it. It's pretty much the social norm in the Drupal development community to push the platform. You can probably expect it to continue in its forward direction. Drupal 5 saw quite a few improvements, and several concepts partially implemented that haven't come to full fruition yet. Output rendering as formAPI constructs is partially implemented, right now the node output is rendered FormAPI style, but isn't being leveraged. Configurable node types found their way into core, but the field management aspect of CCK has been completed. There is method within the madness though it may not be well documented and releases need to keep coming to see the partially implemented concepts completed. It's a non-blocking development process that leads to a lot of innovation I believe. Release Often, Release often, release often. As far as new changes I think are coming in Drupal. - split hook_menu into hook_router? & hook_menu - cck fields working their way into core. - abstracted data definition language and api. - openid replaces drupal's existing distributed auth. - newer cooler form elements and widgets. In contrib it would be nice to see modules continue to leverage FormAPI better, some new FormAPI manipulation modules, and some modules can use a good overhaul. The learning curve from version to version is harder to get over than then initial learning curve for me. I have to rid myself of old habits, but normally there are only a few real changes needed to existing modules. I ported the few I maintain from 4.7 to 5 in a period of hours. DISCLAIMER: These are all just my opinions and delusional dreams. There is no real roadmap, and the only things that get done will be those people choose to do for whatever reason they choose to do it. Are we already at Drupal 6 though? Can't a brother get a minor release? .darrel.
On Wednesday 31 January 2007 4:03 pm, Zohar Stolar wrote:
Finally, and this relates to a parallel discussion about maintaining "old" modules, we must remember that our clients (we do work for them, eventually), can not all afford upgrades so often. This might sound idiotic, but it must be taken into consideration. Smart clients, and most of them are, are studying the market well before investing in such a content platform, that is becoming more and more centric in business. If we move too fast for modules' maintainers to upgrade their modules, we'll end up with a very advanced CMS, but our sites won't survive more than a year.
OK - while writing this I already received two excited mails about the date (Dries is a year behind, go to sleep... or wake up! ;-) ), and anyway, I'm reaching the midnight barrier where I'm at (remember - no posts to the list after midnight for the sake of our sanity :-) ), and I wrote too much (maybe I AM becoming too old....), So I'll just finish with a small proposition: let's try to at least make n effort and prepare the community for the changes. Periodic posts about tendencies in the development will soften the shock when D6 lands here.
Good night all, Zohar
To come back to the original topic, note that we're not talking about releasing Drupal 6 on 1 June but freezing it. Given the freeze length that the last two versions of Drupal have had, I suspect an actual release would then happen somewhere around Thanksgiving. (That's late November for you non-United Statesians.) I'm not going to get into the good/bad question, but I will say that is at least consistent from what I've seen. :-) Personally, what I'd really love to see in D6 is value-add rich-content fields (CCK). As I mentioned a few weeks back, right now you can either write a CCK field and add it to a node manually OR you can value-add more primitive elements dynamically, but you can't do both (AFAIK). I don't know if anyone is working on a way to let us have our cake and eat it too (without hosing SQL performance), but if someone is please let me know in case I am able to dig up some time to help. :-) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com 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
participants (16)
-
AjK -
Darrel O'Pry -
Dries Buytaert -
Dries Buytaert -
Gerhard Killesreiter -
James Walker -
Jeff Eaton -
Karoly Negyesi -
Khalid B -
Larry Garfield -
Laura Scott -
Robert Douglass -
Scott McLewin -
Stefan Borchert -
Victor Kane -
Zohar Stolar