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...