Slashdot Mirror
Drupal 8 Development Begins — 15 Bugs At a Time
darthcamaro writes "It took nearly 3 years for the open source Drupal 7 content management system to hit general availability. The plan for pushing out Drupal 8 is to be faster. How are they going to do that? '"At no point in time will there be more than 15 critical bugs," Dries Buytaert, founder of Drupal said. "I will not pull in a big change if we know there are known bugs. This gives us the ability to do timely releases because we know at most the release is only 15 critical bugs away from being ready."'"
Two bad side effects may be:
- Less merging (which will slow progress)
- More critical bugs triaged as non-critical to avoid blocking releases.
I like the Chrome team's ideas to have multiple branches, only do merges in one direction (towards more stable branches), and making features easily removable so they can be nuked if they are not stable enough to make a release. I'm not sure of a clean way to do the easy code disabling with PHP.
http://goo.gl/G2uDn
In general, though, more merging is better than less merging. It will be interesting to see how this pans out for Drupal.
Because I always know about all of my bugs and keep track of them while I'm programming. In fact I sometimes even plan them ahead of time.
This was like when they said that once there were no more critical bugs 6 and then 7 would be released. Which is what happened. They moved the level down to major and voila! No more critical bugs.
Now, a few days after 7 was released, 7 criticals appeared. 2 were new. The others? Just old bugs that could be bumped up again.
No one needs more than 15 critical bugs.
rewriting history since 2109
This is the 5th drupal psuedo-story in the duration of a month ?
REALLY ?
And on EVERY ONE OF THEM, unity100 whines about it and slips in more links to his pet framework that nobody uses.
I find that differentiation between 'bugs' and 'known bugs' scary (to say the least).
Does he mean that there will be no more than 15 critical bugs (whether known or unknown)? Or, does he mean that all bugs are always known (and that when the 15 errors mark is reached, one simply has to stop writing new code to keep on that mark -since undetected bugs don't exist-?)
In any case, it is very naïve. Naïve and frightening.
HermesPod: Free Podcast Download Manager for Windows
Look at who started using Drupal in the last year or two: The Economist, The Grammys, Fast Company, The Examiner, House.gov (and all ~535 house websites) recently moved to Drupal, Energy.gov, WhiteHouse.gov, and here's a list of some 120 national governments using Drupal.
But hey, Drupal only has 2% market share of all sites on the web, is being adopted by government and corporate organizations at a maddening pace, and just had their first major release in 3 years. There's no reason why this Drupal shit should be discussed on Slashdot.
sysadmins and parents of newborns get the same amount of sleep.
Big and getting larger. Drupal is pretty awesome once you figure it out. I hated it at first and couldn't understand why it was loved by some but definitly understood why other loathed it. But then one day it all made sense and I couldn't believe the amount of power afforded the developer in making insanely cool Websites relatively fast and the few defects you're left with because a lot of the things that would cause problems are taken care of for you.
"If you are a dreamer, a wisher, a liar, A hope-er, a pray-er, a magic bean buyer
The definition of framework has nothing to do with the size or difficulty of the codebase. From what I can tell from the project's website, it fits the definition.
Drupal, on the other hand, is a CMS which includes a framework (for the modules/plugins).
Dilbert RSS feed
That framework you're constantly advertising ... dear god, it's the most terrible abuse of singletons I've ever seen in my life. Please, for the love of all that is holy, learn design principles.
BeauHD. Worst editor since kdawson.