[drupal-devel] Release schedule
Hello world, just an update on the status of the Drupal 4.6 release. It has been exactly 10 days since the code has been frozen, so somewhere next week, I'd like to 'roll' a first release candidate and ask early adopters to start testing what will be Drupal 4.6. For this to work, 1. We need an upgrade path for PostgreSQL! 2. We have to verify the accuracy of the help texts. (I fixed some broken links earlier today and I'm sure there are more.) 3. We have to work our way through some bug reports, and the critical bug reports in particular. A list of all critical bug reports can be found at: http://drupal.org/project/issues?projects=3060&states=1&priorities=1. 4. We have to further improve the usability and consistency of Drupal 4.6. -- Dries Buytaert :: http://www.buytaert.net/
On 11 Feb 2005, at 12:20 AM, Dries Buytaert wrote:
1. We need an upgrade path for PostgreSQL!
I spent today working on it. The patches will start flowing in the next day or two. -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
Dries Buytaert wrote:
Hello world,
just an update on the status of the Drupal 4.6 release. It has been exactly 10 days since the code has been frozen, so somewhere next week, I'd like to 'roll' a first release candidate and ask early adopters to start testing what will be Drupal 4.6.
For this to work,
1. We need an upgrade path for PostgreSQL!
Adrian, can you give us an update on the PostgreSQL port/updates? I'd like to make a RC available during the weekend. Should we go ahead without PostgreSQL? -- Dries Buytaert :: http://www.buytaert.net/
Sorry, as someone who hasn't really contributed much to Drupal, it's not really my place to say... However, I feel it would be good not to rush the release so that all the bugs can get ironed out. Could we make it an 'Alpha' for the weekend, to encourage testing and more bug fixing. It would be good to have more time for the most popular contrib modules to be tested with the various changes that have happened (image api etc), and for documentation to get updated. Once you release 4.6 and lift the feature freeze, not many more bugs are going to get fixed! I'll even promise to help (with the bugs and testing)! Cheers, Ross. Dries Buytaert wrote:
Dries Buytaert wrote:
Adrian, can you give us an update on the PostgreSQL port/updates?
I'd like to make a RC available during the weekend.
Should we go ahead without PostgreSQL?
On Fri, 18 Feb 2005, Ross Kendall wrote:
Sorry, as someone who hasn't really contributed much to Drupal, it's not really my place to say...
I disagree. This depends much on what you say. And how you say it.
However, I feel it would be good not to rush the release so that all the bugs can get ironed out.
This is just the point of having release candidates.
Could we make it an 'Alpha' for the weekend, to encourage testing and
The name really doesn't matter.
more bug fixing. It would be good to have more time for the most popular contrib modules to be tested with the various changes that have happened (image api etc), and for documentation to get updated.
That's the whole point. :o)
Once you release 4.6 and lift the feature freeze, not many more bugs are going to get fixed!
This is contrary to experience.
I'll even promise to help (with the bugs and testing)!
That's good.
Dries Buytaert wrote:
Dries Buytaert wrote:
Adrian, can you give us an update on the PostgreSQL port/updates?
I'd like to make a RC available during the weekend.
Should we go ahead without PostgreSQL?
IMO yes. Maybe we should put a "PostgreSQL developer wanted" sign on drupal.org. Adrian clearly is too busy to do it alone. Cheers, Gerhard
participants (4)
-
Adrian Rossouw -
Dries Buytaert -
Gerhard Killesreiter -
Ross Kendall