Drupal 4.7 still a moving target :-(

Today I got back to Drupal development after a few days just to find, to my astonishment, that things are still changing and instead of bugfixing we are still implementing new features.

And worse, new features that break backwards compatibility . So updating modules again, and again, and again...

And of course, new features will *always* introduce new bugs. And that's exactly what I've found today, a new one that breaks one of my modules and in addition to that breaks one of the standard themes :-(((

As I am one of the many people out there that just cant keep up with the the mailing list and the issue queue, I'm about to give up having the module up to date before we have an actual stable release :-(

But what worries me most is that we don't seem to have clear enough what we are doing right now. Or maybe it's just me, but...

WE ARE TRYING TO PRODUCE A STABLE RELEASE, aren't we?

If so, then please, let's go for it, let's do one thing at a time and then, after Drupal 4.7 is out we may have time to care about lots of new very nice features. But if we waste our time now updating modules once and again that's just it: a waste of time.

NOTE: Whatever, I'm quite happy about how Drupal 4.7 starts looking. Only I'd like to see it out at once. Ok, maybe I'm a bit angry today -sorry-. I think I'll go for a beer and will get back tomorrow...

Comments

Feature?

What new feature(s) are you talking about?

Hi Dries,

Hi Dries,

I think the specific one that broke my site was this one http://drupal.org/node/13148

and maybe the base_url, base_path thing

You can call it a bug or a feature, but the thing is I think it's too late in the process to go changing global variables, output of core functions and things like that...

I'm already updating sites and modules to be ready for 4.7, so when I see things like this I can't help thinking 'fuck, this still keeps moving...'

Cheers!

Release candidates are the

Release candidates are the stable ones, not the beta. You shot your own foot, son.

4.7 RC is here : any news on the i18n module ?

First, thanks for the work on this absolutely must-have module for Drupal.
Now that Drupal 4.7 has been released, do you think you will be able to release an update of this module ??
Thanks again for your work (previous and to come :p) !!

Drupal 4.7.0 released

Finally..
Today, Drupal 4.7.0 is finally released, I am just waiting for i18n to be updated for 4.7 before I upgrade my site.
Time for you to work Jose :-)

Well, it is hopefully stable

Well, it is hopefully stable enough. I am going to give a go to your i18n module...

Drupal's design

I totally agree. Drupal will not be a CMS that people should use until it has a commitment to support APIs and documentation that doesn't literally scorn those who can't keep up with the mailing lists, chats, and numerous other channels. Despite claims of Drupal being "like" designed systems (like this comical document, http://api.drupal.org/api/HEAD/file/developer/topics/oop.html... fudge fudge fudge), Drupal at its heart is very much at the whims of its core developers.

i18nblock.module & default language

First of all Joe, thank you for a wonderful module. I really don't know what to do w/o it... Secondly, I'm running into several problems, can you help?

1. I don't think the current i18nblocks.module is compatible with the taxonomy_block module (it doesn't save the selected menu)

2. I would like to default my website to another language (other than english), how would I go about it? I was already changed the default language to IT and added IT to the settings.php file (www.mysite.com/IT) but english is still showing when launching my website.

Thanks