Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Finding an issue to work on is hard. But it is harder while Drupal Core is in Release Candidate mode, because you may have found an interesting issue and decide to spend some time on it, only to find out later that it won't be committed because of the RC.
Proposed resolution
Add a dismissable notification banner when somebody goes to a core issue page while we are in RC.
This message would be shown only the first time you visit a core issue. Maybe restrict this to only issues in the 8.0.x version. The issue summary would say something like:
drupal core is currently in a release phase when only certain issues are commitable, for more information go see https://www.drupal.org/core-mentoring/novice-tasks#avoid
Comments
Comment #2
jackbravo commentedComment #3
yesct commentedThank you for making this issue.
We might even want it to be more generic. As this information could be useful before RC, during, and after release also. (but what is allowed will be different, so we can link to a page that we can update (maybe an existing page, maybe a new page).
Instead of
drupal core is currently in a release phase when only certain issues are commitable, for more information go see https://www.drupal.org/core-mentoring/novice-tasks#avoid
Maybe
Depending on the current release phase Drupal Core is in, only certain issues are commitable. For more information see the handbook page about release phases.
Comment #4
yesct commentedComment #5
Bojhan commentedIs this really possible to do programmatically though?
Comment #6
drummThis sounds like it is related to #2013222: Add "Issue tasks" to project issues and correlate tasks with handbook documentation. The whole instruction manual for an issue should go in one area of the issue page.
Project node types currently have a project_issue_guidelines field, which is shown when creating an issue. Another field next to this would be the place to put the data. Then a new block would handle displaying it appropriately.
Dismissing should probably be an AJAX request to keep what was dismissed per-project in the DB. I'd recommend local storage, but wouldn't want to risk running into limits.
The project maintainers would be responsible for updating the instructions as they enter different phases of development.
Comment #7
darol100 commentedA form wizard base on the handbook to determine if the patch is going to be submitted in RC or the next version. I have open a separate issue for the form wizard #2600894: Form wizard that will determine if an issue is appropriate for this phase of the release.