Proposal: consolidation period for D10.0.0

Created on 22 November 2022, about 2 years ago
Updated 2 May 2023, over 1 year ago

Problem/Motivation

There are a very large number of outstanding issues that are important enough for those using composer to patch core with multiple fixes, which to my mind is not a good thing. It increases the fragility of the ecosystem and makes core and contrib maintainers lives harder, as well as extending the already very high bar for Drupal site developers.

Proposed resolution

Once Drupal 10.0.0 is out I suggest that the core maintainers impose a period of time during which only fixes for pre-D10 issues, important D10 fixes, but not further features or changes, are applied. I would suggest ~1-2 months for this. Hopefully the issue count can be reduced noticeably.

I would also suggest that a similar thing (a period of consolidation and only-bug-fixes) was done on a regular basis: Ideally this one would be before D10!

🌱 Plan
Status

Fixed

Version

10.0

Component
Other 

Last updated about 1 hour ago

Created by

🇬🇧United Kingdom rivimey

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇳🇿New Zealand quietone

    @rivimey, thanks for presenting your thoughts on reducing the number of outstanding issues. I discussed this with the other release managers. We think the next step is to determine if we can get stats on patch downloads. This can then be closed because catch has responded to the other points.

    I will also add that there is Slack channel, #needs-review-queue-initiative, which has made excellent progress is keeping the needs review queue at a manageable size. This is being accomplished by completing many issues that had a working patch but for some reason (docs, issue meta, tests, etc) was not ready for commit. That effort contributed to the increase in the number of commits in late March and early April.

    Regarding the stats, I have created 📌 Get patch download statistics to inform core issue triage Active . However, longwave remembers asking about this and stated "either the DA was unsure if they even had them or it would be a lot of work to get them'.

    I am also adding this issue and the new one to the Issue Summary of 🌱 [meta] Improve issue management Active in an attempt to keep all these ideas in one place.

    And I see these questions that I can answer.

    perhaps the state "-- open issues --" could be adjusted to exclude Fixed and PMNMI, which would IMO be reasonable?

    This would be quite a change and effect all projects and people's bookmarks so I think a separate issue is warranted. That would be in Drupal.org Customizations , unless I am mistaken.

    Is there a more detailed, perhaps interactive, version of the dataset used by https://lendude.gitlab.io/bug-smash-initiative/ ?

    No, the data is gathered from d.o. The code for the project is at https://gitlab.com/Lendude/bug-smash-initiative

    I am closing this as Fixed. If I missed something and there is more to discuss, re-open the issue and point out what was overlooked.

    Thanks.

  • 🇩🇰Denmark ressa Copenhagen

    Great discussion, thanks! To lower the bar of entry, and get more eye balls on contrib module bugs, and produce solutions for them, but also speed up wider usage of contrib modules, I have created Always allow downloading and installing contrib module dev-release in next major version Closed: duplicate .

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024