Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.D8 RC1 will attract major attention, and we want it to. Many new users will try out D8, and many will spend a lot of time site-building on it, even if they are warned of the risks of doing so.
There are currently many major bugs in D8. Bits of the UI that do not work as advertised, etc.
In theory the issue queues document all these. But to anyone who is not already a D8 expert, they are difficult to penetrate, and impossible to survey. Imagine you wanted to brief a sitebuilder colleague as to what bits of D8 they should not expect to use at the moment. How would you even begin to do that?
Enormous amounts of user frustration - and damage (even though unfair) to Drupal's reputation - could be alleviated by a regularly updated "Plain english guide to outstanding major D8 bugs", which could be prominently linked to from D8 release notices etc.
Comments
Comment #2
cilefen CreditAttribution: cilefen as a volunteer commentedIt is actually hundreds. One way non-expert contributors can help is this:
#2474049: [meta] Major issue triage
Comment #3
webchickHaving written the "plain English guide to the criticals" a few times:
- http://www.webchick.net/critical-rundown-bogota
- http://www.slideshare.net/webchickenator/plain-english-guide-to-drupal-8...
- http://www.slideshare.net/webchickenator/acquia-drupal-8-hackathon-demo-...
...I can say that even writing this for even a small handful of issues is an enormous undertaking, taking hours or sometimes taking days per issue.
There are over 400 major bugs. This is not something a single individual can reasonably take on, and possibly not something that's able to be taken on.
I would echo @cilefen, and encourage anyone passionate about this to form up with likeminded others and tackle #2474049: [meta] Major issue triage, documenting as you go.
Comment #4
webchickTo assuage your fears somewhat though, remember that:
- Drupal 8 is going to be ".0" software. People expect .0 versions of all software to be buggy, and will avoid them in favour of later versions if they care about stability.
- Most people will not even touch Drupal 8 until there's a critical mass of contrib modules available, which is unlikely to be in the first few months of D8's release.
So we have quite a bit of runway to clean this up, IMO.
Comment #5
jhodgdonIs this issue actionable? If not, let's please close it. As it is, it sounds like some kind of a policy thing.
Comment #6
webchickYeah, I think this is "won't fix," personally. The effort is simply too great.