Drupal 7 status update and release plan
Drupal 7 is moving along nicely, and is becoming increasingly stable. We just released a second alpha release, fixing a number of critical bugs, following our initial alpha release in January. Alpha releases are to give Drupalistas something to download and test, so they can report and help fix bugs.
When will we switch to betas? We will switch to betas when the upgrade path from Drupal 6 to Drupal 7 is working. Once we hit beta, we will become increasingly strict about accepting any more changes and we'll also commit to making HEAD to HEAD upgrades work.
Finally, we'll start rolling release candidates once the number of critical bugs is zero (or close to zero). To help us focus on critical bugs, we're working on adding a 'major' severity level to our ticketing system, making the options 'critical', 'major', 'normal' and 'minor'. 'Major' bugs would be really bad, but not necessarily block a release. For example, bugs that don't prevent Drupal from working, or that only affect a fraction of the Drupal population would be prioritized for fixing in follow-up releases. Critical bugs are those that badly break Drupal, or that are a major regression compared to Drupal 6.
Where are we right now? There are currently about 150 remaining bugs that need to be fixed. These bugs are real, and not always trivial to fix because a lot of background and domain expertise can be required. As a result, some bug reports seemingly depend on one or two people to fix them. Therefore, it is very important that we encourage and mentor new people to help fix some of these difficult bugs. I'd like to ask all sub-system maintainers to watch their sub-system's issue queues closely (like Moshe did recently), and to provide the leadership to help us make progress. If we do and we work hard, I think we can still release Drupal 7 in Q2. If not, I'm worried that Drupal 7 might not be released until Q3.
In other words, let's all try to put some extra time and effort into fixing the remaining bugs, and let's start to be laser-focused on the critical ones. It would make for quite a party if we could roll a first release candidate in time for DrupalCon San Francisco on April 19th. I would have to sing on stage from happiness, or something. Thanks!
Is that official?
Can I hold you to that?
if ($date > 04192010 && $date <= 04212010 && $drupal_ver >= 7xRC1) {
dries('get_on_stage');
dries('sing');
}
? :)
.cw.
lmao
lmao classic
---
Web Developer For //_Semicolon; South Africa
My Blog
Twitter
LinkedIn
:-) can't wait
:-) can't wait
So Dries will sing in any case?!
I suspect Drupal 7 will be released before April 20th, 2012. In your own date format, $date = 04202012. Since, (04202012 > 04192010 && 04202012 <= 04212010 && $drupal_ver >= 7xRC1) is true, I can tell you for sure that Dries will sing. It's only a matter of when and what.
Unless, there's a bug in the code and it should be ($date > 20100419 && $date <= 20100421 && $drupal_ver >= 7xRC1)... ;)
Best wishes,
Andrei.
I would think...
it would either be
get_on_stage('dries');
or
Dries::get_on_stage();
unless dries() is very robust.... no comment.
-------------------------------------------
Sam Tresler
http://www.treslerdesigns.com/
lmao
lmao
PC Pro Schools - WI.
I'm looking forward to
I'm looking forward to it.
Good luck ^^
Still waiting for it
Hope success for New Release,..
Thanks
I would like to assist with
I would like to assist with bugs if I get some time freed up in the next month or so.. it will also help me to learn the changes to Drupal 7 API.
What's the best way to get involved and collaborate?
==============
drupal web development
catch me on twitter
To get involved...
If you click on "Contribute" on the top Drupal.org navigation menu, and from there click on "Development", there are a couple of pages that will give you some pointers about what you can do to help and how to get set up and communicate with the rest of the development team.
Rather than repeat those suggestions here, I'll just point you to the link: http://drupal.org/contribute/development
Thanks for your willingness to help!
Thank you
Thank you
==============
drupal web development
catch me on twitter
Will migrate!
If Drupal 7 is not released in Q2, I may migrate to Wordpress.
Just kidding!
Can't wait for D7 stable!
Can't wait for D7 stable! Already testing it on my machine. Hoping it gets released in Q2 as well.
I am somewhat concerned that
I am somewhat concerned that the new 'major' status will mean that critical bugs are let out into the release and affect stability of the first proper release.
Perhaps we could have some confirmation that true critical bugs will remain marked as critical rather than using the 'major' get out clause?
Currently working on: Drupal Demo Sites (now in public beta).
Major = Release Blocker?
Dries, I think you should clarify if you intend the major bug level to be a show stopper bug or not. Do "major" bugs categorically block the release of the next version?
Definitions...
Criticals block release, Majors are "Wow, that's really bad!" but will not block release.
Here's what I would see as a typical example of where this breaks down, just from a random sampling of the issue queue right now:
Upgrade path doesn't work: critical; we absolutely cannot release Drupal 7 with a broken upgrade path, for hopefully obvious reasons.
Shortcut module completely lacks test coverage: major; This is a really bad problem, since we are actively introducing regressions right and left while this module lacks test coverage, but it does not prevent us from releasing. It's something we should definitely have as a high priority, though.
Right now, both of these are labeled "critical", because the next step down is "normal" and an entire module missing test coverage is definitely way more severe than "normal." Distinguishing these types of issues (in addition to really nasty bugs that happen to exist in all Drupal versions and therefore can't qualify as 'release blockers') is what the new "major" priority will be for, so we get an accurate picture of how close we are to 7.0.
Hope that helps!
A stable release is better than an early release
Producing a stable release is the important thing, and the D7 developers have made fantastic strides towards making that possible. I hope you don't fall at the final hurdles because you're trying to match an arbitrary schedule. And don't lower your standards just so that you can say that there aren't any more "critical" issues remaining (after all the emphasis on testing, would you really consider a final release if a core module had no tests???).
(Although I think webchick is saying that "Major" issues most definitely should be addressed before a release, but there might be circumstances that cause them to be left unresolved. I guess I'm just saying that those circumstances shouldn't be purely time-related.)
The prospect of a Q3 release shouldn't be something to "worry" about. There's no need to cut corners. Drupal 6 remains a good platform in the meantime.
I agree
@jweowu - well said, I agree. There is no hard and fast rule that every major release have to take place every 3 or 4 years or so. Think of users that has to manage actual content and not the CMS itself - product released with "major" bugs are still bugs and the hapless user has to upgrade and upgrade, and upgrade.
If that has been the rule how softwares worked, well there can be a pardigm shift now just like some components that are introduced in the new Drupal. How about a really very innovative and user friendly way about a release - hand over a complete release, for a change? Is there anything impossible? Solve it/those for a change.
stable release
Introducing a new classification for bugs sounds a bit like the government announcing a drop in unemployment figures after changing the way they measure unemployment.
Totally agree that producing a stable release is the most important thing, not the timing. Drupal 7 is bound to get a huge amount of press when it is released and I think getting the D7 release right is vital for the credibility of the community. This includes having an awesome stable core product, and stable releases of all major contrib modules.
Drupal Developer
On stability...
The thing to remember about Drupal 7 is it's the first release in Drupal's history with almost 18,000 automated tests, and counting constantly re-verifying that everything's working properly. We know all the test-covered stuff is working, which is pretty much all of the critical path that folks would use day-to-day, plus a whole bunch of of the tweaky edge-cases that we would be likely to break again without test coverage. Directly as a result of this, Drupal 7's general stability, even in alpha, rivals that of the first couple of point releases of the 5.x and 6.x series.
What we honestly need are more people trying out Drupal 7 and finding the really bad bugs we've missed, and helping out in the core queue to squash them. But read the responses here. People are "looking forward" to its release and "can't wait" for it to come out. The simple fact is, the vast majority of the community (and their employers/clients) won't really start to care about (and develop/port modules for) Drupal 7 until we hit 7.0. So, as paradoxical as it sounds, releasing is key to Drupal 7's stability.
There's sound logic in identifying and calling out the the really bad bugs that will hit absolutely everyone and cause significant problems, and separating those from the "Dang, we really ought to fix that." kind of bugs. This way, we direct our volunteers to focus on those that will have the biggest impact, and then can attack the second round of bugs with far more resources than we have available now.
But absolutely nothing stops you from focusing on the "major" bug queue, and we'll certainly commit those patches, too! :)
I'm also concerned about the
I'm also concerned about the 'major' priority being mis-used, but it's down to people who work on core - which can in include YOU! ;) to keep an eye on the critical issues queue, and the major one when it's added, and make sure things are in the right place.
At the moment, we can't downgrade something from critical, without bumping it down to the 'normal' queue, which has hundreds of issues and isn't any where near as well maintained as the criticals queue. Major allows us to highlight bugs that need fixing ASAP, without having a bloated queue of release blockers which really aren't.
webchick's example of the shortcut module tests is a good example. Drupal 6 released with zero test coverage. The shortcut module is enabled in the default install profile (which is what we test with), so some of the code is tested indirectly anyway. If we get through the 143 critical issues in around 6 weeks, and the only remaining one is tests for shortcut module, then that's not going to block a release. More likely, is that it, and many other issues, will get bumped down to 'normal' or moved to Drupal 8 as we start releasing more alphas/betas - this is usually anything in the category of 'nasty bug, but very obscure and hard to fix' - which is really what major should be.
Keeping those in a small, well managed queue of major bugs can only be a good thing. Also the overall size of the 'major' queue will be some indication of Drupal 7 stability, whereas as the normal bugs queue isn't at all - could include bugs fixed six months ago for all we know, because the number of issues is far to high to keep track of. When the criticals queue is down to 5 or so, if we have 200 bugs in the 'major' queue, then we can always move some up to critical if we want to delay the release a little bit longer. Where the lines actually are is something which needs to be figured out, likely on a case by case basis.
(critical,major,normal,minor) ~= (critical,high,medium,low)
Immense kudos to the core devs on their tireless grappling with some very, very complex issues.
I made noise earlier about Drupal moving to Launchpad or similar. Launchpad also has four severity levels. Coincidence?
...probably :)
I am excited, as I am
I am excited, as I am struggling to understand why I have to install 20 plugins right away with Drupal 6 to get any kind of usability without coding. I can't thank the developers enough for this.
auto insurance
Health Insurance Quote
Florida Public Adjuster
-
It's a modular cms framework. It simply makes the cms more flexible. If you could blink your eyes and everything was done for you, then you would have less flexibility.
http://picxelplay.com
write>read>preview>edit>read>post
waiting....
waiting....
Drupal User Assocication--Drupaluser.org
Where do I post bugs? I have
Where do I post bugs? I have the Alpha2 and I can't get past "Configure Site" without a long list of warning about the date format. And, don't suppose to be able to configure the site's admin and password. Other than the warnings I just have a empty page.
_____________________________________________
Coding is like a box of chocolates!...
Blend 2.0.1523.0
VS2008 9.0.30729.1 SP
Vista Ultimate, RAM 8GB, 64-bit OS
Virtual Server 2005 SP1, Web Server 2008 R2
NVIDIA GeForce 9500 GT
Intel(R) Core(TM)2
Start from the project page...
To post an issue on any project (Drupal, a contributed module, a contributed theme, etc.), I suggest starting at the project page. In this case, http://drupal.org/project/drupal
You'll see a box on the left sidebar marked "Issues". Search to see if your issue has already been reported first, then report your issue.
Two pages/sections that you can read for more information:
Report a problem: http://drupal.org/node/314185
Use the issue queue: http://drupal.org/node/317
Thanks!
Thanks!
_____________________________________________
Coding is like a box of chocolates!...
Blend 2.0.1523.0
VS2008 9.0.30729.1 SP
Vista Ultimate, RAM 8GB, 64-bit OS
Virtual Server 2005 SP1, Web Server 2008 R2
NVIDIA GeForce 9500 GT
Intel(R) Core(TM)2
Upgrading D7 releases
Could someone confirm that there is an upgrade process for the D7 Alphas/Betas?
I would like to start playing with D7, but not if everything I do cannot be transfered to the next Alpha/Beta.
Thanks,
Mike.
Oops
I just answered my question by RTFM :-)
So, no upgrade path between pre-release D7s :-(
There's no guaranteed upgrade
There's no guaranteed upgrade path, and you currently can't upgrade from Drupal 6 to Drupal 7 safely. However we don't go out of our way to break the upgrade path between alpha/beta/rcs either. If you only want to play around, and keep backups each time you upgrade, then you have some chance of not running into issues - and more importantly, can help make the upgrade path more stable by testing it and reporting bugs back.
How can we know?
Is there any way we can find out, when a new alpha/beta/etc comes out, what kinds of things *would* break the upgrade path?
The reason is that I have a very small test-case site in A1--I really wanted to try D7, but I also knew full well what I was getting myself into. I'd love to have it in running the full releases when they come out, and it would only take a few minutes to transfer everything manually if need be.
But if I can somehow get an idea of what would break, I could possibly fix those things myself even if there's no official upgrade path. And if that somehow helps the testing effort, all the better. I just don't feel confident attempting it just by looking at the release notes from release to release.
please don't release it until
please don't release it until it really becomes stable and capable to upgrade themes,modules and core to D7
Messaging and notifications
D7 looks good, but what is to me a major pair of modules is missing any sign of D7 activity. I'm not up to coding at present but could probably help test.
which modules?
which modules?
Drupal Developer
Hi there to all the Drupal 7
Hi there to all the Drupal 7 development team...
I was wondering weather there would be any feature added to the forum module or not, I mean a forum such like vBulletin, so we wouldn't need to use other forum apps such as vBulletin or PHPBB...
By the way, would there be a possibility to let the admins to change the directories URLS, for example; BASE_URL/admin/ can be changed to whatever the admin wants... like BASE_URL/whatever/ etc.
How about the theme section, would it be same as Drupal 6, or new features will be added to...
By the way, by when we shall expect a stable release... so we can use it publicly... not in localhost....
Thanks to you all, really appreciate the work, keep up the good work...
:)
I don't know if the forum
I don't know if the forum module will be as extensive as phpbb/vBulletin/IPB but you can check out Advanced Forum module. If not, you can certainly build a bridge between platforms by authenticating users through Drupal and other mods if you so wish.
==============
drupal web development
catch me on twitter
.
Core forums haven't changed much. But Advanced Forum will be ported to Drupal 7 at some point.
Michelle
---
Coulee Region Online: Social networking and area information. You're welcome to visit but please don't make an account unless you want to join the community.
Posts/comments as nodes
dazraf wrote:
> I was wondering weather there would be any feature added to the forum module or not, I mean a forum such like vBulletin, so we wouldn't need to use other forum apps such as vBulletin or PHPBB...
The new alpha versions of Advanced Forum (6.x-2.0-alpha2 currently for D6, and later for D7) are adding support for nodecomments, which seems very promising to approach the functionality of standard forums, where all posts are treated equally. This will allow easier migration to Drupal from standard forum systems, and advanced administration such as thread merging, etc., without need for node-comment conversions and therefore without losing chronological order, etc.
Drupal 6 or Drupal 7
Hi Dries / Drupal Professionals
I want to use Drupal for my personal website Blog on to a third party hosting server. I am going to start my work from April first week.
I was wondering ... should I wait for Drupal 7 or continue with Drupal 6 .. As I am going to use lots of Drupal modules... Even if I start my work in Drupal 6 .. can I port the whole website to Drupal 7 ..
Please suggest ..
Thanks
Apratim
P.S - I am only a starter ... :-)
Apratim Bose
Start with Drupal 6
Drupal 6 would be a great place to start. if you want to gain a lot of the practical benefits that Drupal 7 will have over Drupal 6, you can install the following modules:
Modules
CCK
Views
Display Suite
Node Display + Node Display CCK
Admin_role
Date
ImageCache
Filefield
ImageAPI
Feeds
Themes
Seven
Get D6 now!
Well, I would suggest you to get Drupal 6 now! According to me, Drupal 6 is the strongest and will be the strongest at least for next 6 months. A wide range of modules are available for it. And you can also upgrade your Drupal 6 installation to Drupal 7 easily. Good luck!
//
Help me build drupaldaddy.com. Write to me!
Find out about major changes?
If I were to start prototyping a new site from scratch using Drupal 7 alpha where would I look to find the major differences from what I did in Drupal 6? e.g. where would I find out if there was a completely new way of theming?
try the upgrade guides...
Lots of info about the differences between 6 and 7 here:
http://drupal.org/node/224333 (modules)
and
http://drupal.org/node/254940 (themes)
Drupal Developer
So coooooool!
Drupal 7 is sooooo freaking amazing!
http://picxelplay.com
write>read>preview>edit>read>post
drupal 7 release timeline
is it possible to say when drupal will release drupal 7 stable version?
i think this is essential for planing on migration, i have a site designed by drupal 5 and i am confused that do i upgrade to drupal 6 or waiting for drupal 7 stable version?
رزومه فارسی من:
http://drupalers.net/files/persian-cv.pdf
my resume (English):
http://www.drupaldevelopers.net/profiles/esmailzadeh
No
It's released when the critical bugs are out and the core maintainers decide it's ready to go. When that happens depends on how much people help and how fast the bugs get squashed.
Michelle
---
Coulee Region Online: Social networking and area information. You're welcome to visit but please don't make an account unless you want to join the community.
Debian/Ubuntu
As Dries pointed it out, release time acts as a major motivator for both testers and developpers.
david thanks for your helpful
david thanks for your helpful information and link
it seems Drupal are using Debian method for release new versions. (and can not use Ubuntu method)
رزومه فارسی من:
http://drupalers.net/files/persian-cv.pdf
my resume (English):
http://www.drupaldevelopers.net/profiles/esmailzadeh
Wow, nice
Basic question from a user for an update after five weeks of no new information gets the kind of response one would expect from Microsoft.
Real impressive. And so helpful.
Thanks Michelle!
-
Listen to Dries' keynote speech from DrupalConSF. That should give you everything you need. http://www.archive.org/details/Css3TheFutureIsNow
http://picxelplay.com
write>read>preview>edit>read>post
_
How many ways are there to say it will be released when there are no more critical bugs? In what way can that be said more helpfully? As for new information--that's available to everyone. The critical bug count is in the 'contributor links' block as well as http://drupal.org/project/issues/drupal?status=Open&priorities=1&version....
Your registering a brand new account just to take a pot shot at Michelle is pathetically transparent. Give it a rest already.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
Seems like the critical bug
Seems like the critical bug counter went down pretty steady the last few days. I hope Dries inspired everyone to fix these last few bugs and get D7 out. Remember, this is no Microsoft. This is a team of collaborators, giving you a (great) product for free..
I know the internet generation wants everything now (and for free), but don't let the downers keep you down. Keep up the great work!
- a random Drupal 7 lover
Actually...
... if D7 was released half-baked and full of bugs, that would be very Microsoft-like... When was the last time Microsoft released something only after it was as right as they could make it...? Something in a recent article about a MS architect admitting openly that Vista was released before it was finished, Windows Me was a stopgap, and what about Bob...?
WorldFallz - some people just don't get it... Obviously more a user mentality than a developer mentality, which is the dual-personality of the open source community. I'm right there with you guys on patiently waiting for it to be ready - when it is ready. In the meantime I'll keep downloading and testing the latest builds on my sandbox server...
If I was more comfortable in the core and not afraid to be the proverbial bull in a china closet, I'd definitely be trying to jump into the fray myself... ;)
----------
"Nothing is impossible - it just hasn't been done yet."
Cool Blue Interactive
Octobang
Drupal 7 Sites
Please put the sites running on d7 some where we need it any way. Suggestions are welcome on doing that.
Kind a Drupal 7 Gallery sites where we could all showcase our case study of the sites running on d7.
Drupal 7 and MySQL Cluster
Is MySQL cluster will be supported on this release?
drupal 7 landing page...
This thread is the first that comes up with googling for "drupal 7".
http://drupal.org/node/156281 shows up for "drupal 7 download".
It would be nice to have a landing page for the latest alpha (or beta) with lots of links there.
How to make that happen?
guaka.org - CRM-CMS.nl
issue
Try filing a webmaster's issue.
Michelle
---
Coulee Region Online: Social networking and area information. You're welcome to visit but please don't make an account unless you want to join the community.
Drupal V7 beats Joomla!
Hi!
I had been experimenting with Drupal 6 for sometime now and few features that lacked in it made me not to use V6 for my websites. However, few days back I downloaded the V7 alpha and installed it on my server. The first look was like "WOW" for me. The interface is super!
With the introduction of Drupal7 the major thing that attracts developers like me is that the interface is simple, easy to find and streamlined. Further the adding of "Articles" takes Joomla by its horns. Why I say Drupal 7 wins over Joomla because Drupal now has the Article adding system where Joomla scored over Drupal earlier...further Drupal has built in modules for Blog and Forum which Joomla lacks.
Drupal 7 will be a great success...cant wait to get the stable version!!!!
Thanks to the Drupal development team! ;-)
-Prosenjeet
http://lucknowwebs.com
I would like to take part in
I would like to take part in working out Drupal. There is an experience a writing small CMS. It is possible?