benjifisher → credited quietone → .
I'm going to move the changes for HookOrder to another issue. Assigning to myself for that and to review other local changes before pushing.
@Bojhan, thank you for all your work on Drupal. I've had the pleasure to read your comments while triaging issues and I found them to be very helpful. And thanks for taking the time to reply.
Thanks and best wishes!
Committed to the active branches and updated the project node, google group, slack channel.
Thanks sun for your comments, when triaging issues I always find them helpful.
Committed to the current branches and checked that that the status in the Google group, the core project node, and the Slack channel are correct.
Thanks!
@donpas, thanks for fixing the typo. If you have reviewed your fix of a typo and are sure it is correct, you can probably skip setting the page to 'Needs Review'.
I put the documentation at Guidelines for semantic versioning for contributed projects → in the Creating a new project → .
I did made some changes to make it easier to scan the page and added a into paragraph. The page is set to NR.
I updated the remaining tasks.
And then I noticed that I missed the suggestion by @joachim about a new guide. That seems like a good idea, but it is not strictly necessary to complete this piece of work. The doc can easily be moved later.
Added Mailer to Experimental modules and themes in Drupal core →
Add Mailer, https://www.drupal.org/project/drupal/issues/3379794 📌 [PP-1] Add symfony mailer transports to DIC Postponed , adding that it is for 11.3
In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
Drupal 10 is now in maintenance mode, and there are limited allowed changes for a maintenance minor release → . This change is not eligible for commit.
I suspect that this is still a problem on 11.x, so changing version. Although, this needs to be confirmed.
If this problem was discovered on a version of Drupal that is not 11.x, add that information in the issue summary and leave the version at 11.x. In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Thanks.
Restoring issue template so we can keep track of progress.
I forgot to update the version.
If this problem was discovered on a version of Drupal that is not 11.x, add that information in the issue summary and leave the version at 11.x. In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Also mentioned on the version → section of the list of issue fields documentation. Thanks.
If this problem was discovered on a version of Drupal that is not 11.x, add that information in the issue summary and leave the version at 11.x. In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Thanks.
@terao3, For Drupal core, it is preferred that contributors add a comment that they are working on an issue instead of assigning it to themselves. See Assigning ownership of a Drupal core issue → .
If this problem was discovered on a version of Drupal that is not 11.x, add that information in the issue summary and leave the version at 11.x. In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Thanks.
This also needs the standard issue template so progress can be tracked.
quietone → created an issue.
Changes are made on 11.x first.
I checked again today and I could not find references to removed extension files in 11.x
Thanks!
Changes for new code on 11.x
quietone → changed the visibility of the branch 3515661-fix-doccomment.missingshort-in to active.
quietone → changed the visibility of the branch 3515661-fix-doccomment.missingshort-in to hidden.
Time for another review.
@xjm, thanks.
Back to needs review for the recent changes.
I read the help text added in #2091403: Create hook_help for Entity module → for the Entity module. I then read the field UI help text and found that form and view modes are discussed. There is no longer direct reference to 'entity' in any help text which I am sure is intentional. The concept of 'entity' is not necessary to use a Drupal site.
Therefore I am closing this as outdated. If that is incorrect, explain in a comment and re-open.
@starlightE, thanks for the idea.
I am not able to find any history in core of a 'subheading' content for the Basic page. There is also no support for this idea in the past 8 years. Because of that it doesn't met the Criteria for evaluating proposed changes → . In this case, there is not demonstrated demand and support for the change.
If there is interest in this re-open the issue and add a comment. Or open a new issue and reference this one.
OK, another rebase and update to catch up to HEAD.
The only function referred to in _batch_do is _batch_process() and that has an @see.
quietone → made their first commit to this issue’s fork.
I have gotten this wrong, removing proposed resolution
Updated the IS to be more detailed.
Since the point raised in #20 is specific to 10.6 I think that would be better discussed in it's own issue, a child of 🌱 [meta] Release preparation steps for 11.3.0 and 10.6.0 Postponed .
Maybe we should add this to docs in addition to the metas?
What docs are these?
Added an item to the minor spreadsheet for this.
This came up again in the last 24 hours where the 11.2.0 release highlights needed a small change but I lacked access.
There has been no support for this feature request in the last 9 years. Also, @berdir, explains how to do this in in #6.
Therefor, closing this issue.
That has been postponed for some time waiting for @olli to reply. For what ever reason that hasn't happened in eight years, so I am going to close this. This can be re-opened if there is interest.
@olli, thanks for all your work in VDC and best wishes in you endeavors!
Searched the logs with git log -S'function system_admin_menu' and as far as I can tell this is outdated. I trust someone to correct the status if that is incorrect.
This was resolved in 🐛 There is no way to make a button element that can use the AJAX functionality Needs review .
xjm → credited quietone → .
I removed 'proposed' from the CR and added a screenshot to the issue summary.
Everything appears to be in order here.
This is postponed on 3 php-tuf issues and 1 core issue, so changing status. Update the issue to put the postponed items into the remaining tasks per the guidelines.
Fix formatting in IS.
While this is blocked on https://github.com/php-tuf/php-tuf/issues/396, I am leaving at Needs work because for completing the dependency evaluation.
fjgarlin → credited quietone → .
quietone → created an issue.
Thanks for bringing this up. Those changes were in a section for Windows users and this page is meant to be very basic and directing people to further information. The Local Server Setup guide → has the details for different environments, which is where there is already docs for Windows. Therefor I have reverted that change that added the instructions for Windows and no change is required.
@ adao.boscolo → , thank you for helping to maintain Drupal documentation! The place to add details for installing DDEV with Windows is the Local Server Setup guide → , which is linked to on this page. @ nick hope → has created a detailed tutorial for Windows users in the guide. Please improve those docs, thanks. This page is deliberately kept simple, with links to further information. For background, have a look at this issue, https://www.drupal.org/project/documentation/issues/3398293 🌱 Consolidate local development environment documentation to recommend DDEV Active . Therefor, I am going to revert this change.
Updated the remaining tasks
This looks like a duplicate of 📌 [PP-1] Require PHP-TUF's Composer integration plugin Postponed . That issue has an MR for adding the dependency. I am still comparing both issues.
Adding postponed item to the list of remaining tasks per the issue summary field documentation, remaining task → .
Added dependency evaluation template to the issue summary, with several TBA that need to be completed.
Changes are made on 11.x first.
@longwave, thanks for the review. I made the corrections and checked if any other changes were needed due to the recent update of Coder.
@ressa, is this a duplicate of 🐛 Danish characters ø and å are not transliterated correctly Active .
In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → . Thanks
Drupal 10 is in maintenance mode and this doesn't meet the criteria for inclusion. Does this occur on Drupal 11.x, or 11.2?
There are quite a few issues for view, have you checked for a duplicate?
In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
In Drupal core changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
For reference Percona was added in 2013 in #2062399: Add Percona Server to list of supported MySQL alternative databases. →
Given these factors, the single best piece of advice we can
give is to review between 100 and 300 lines of code at a time and
spend 30-60 minutes to review it
This is from Code Review at Cisco Systems / 63 Code Review at Cisco Systems 2006. This is the study summarized in the report linked from the doc page, the current text in the issue summary.
Further searches only resulted in other articles using the same source.
I updated the handbook page to remove the 'diff size' since we aren't using patches anymore. Let's stay with LOC.
Remove reference to diff size because patches are no longer used.
This was discussed amongst the release managers, @catch, @longwave and myself. We touched on the fact that MySQL is sort of stagnating, but also we have issues to bring MongoDB to core. It was a reminder that any 'recommendation' for a database server may change. But also, we can't drop mention of MySQL, it is still widely used and we test using it. We don't test with a Percona server, so that should be removed. It also come up that we understood the 'recommendation' to be about using a MySQL equivalent instead of PostGreSQL or SQLite, and not necessarily MySQL itself.
As for the text, we agreed that that heading could use an update. And we decided to reduce it to "MySQL, MariaDB, or equivalent".
Update per https://www.drupal.org/project/drupal/issues/3478097 🌱 MySQL should no longer be "Recommended" Active
The allowed changes policy → is updated and the post → published.
I updated credit.
This needs confirmation that the new doc page → agrees with the proposed resolution.
Thanks for the idea. The core ideas project is deprecated.
I asked in committer slack what to do with this 9 year old issue, and in light of the recent strategy direction and Drupal CMS. The produce manager lauriii replied that this can be closed, saying that any work on this idea would be done in the Experience Builder.
Therefore closing.
I should have set this to needs review to get feedback on the proposal.
The core ideas project is deprecated.
The meta issue in #11 is in the core issue queue so I am moving this issue to core.
Based on the last two comments I am closing this as a duplicate. The work is being done in 🌱 [Meta] Make Drupal the first "design-system native" CMS + Unify & simplify render & theme systems Active
Restoring meta data.
Why is this postponed on #3067979: Exclude test files from release packages → ?
I wondered what happened to this issue. This change would make it easier to complete some, but not all, of the core coding standards issues. I also think that core should be consistent in structure. We all know how that can benefit searching and organizing work.
Conflict due to using attributes for @group.
@catch, thanks.
I updated the two doc pages mentioned in the Issue Summary and updated credit.
Add preference for Linux, see https://www.drupal.org/project/drupal/issues/3436617 🌱 [policy, no patch] Drop support for Windows in production in Drupal 11 Active .
Update references to IIS, see https://www.drupal.org/project/drupal/issues/3436617 🌱 [policy, no patch] Drop support for Windows in production in Drupal 11 Active
I checked today and the link in the Issue Summary still shows the action.info.yml file for 11.x. And so is forum, https://api.drupal.org/api/drupal/core%21modules%21forum%21forum.info.ym...
quietone → created an issue.
Changes this to just the jsonapi tests, which are the easy ones. Moving work on the others to another issue.
Changes are made on 11.x, the main development branch first. Thanks.
Checked on 11.x HEAD today, standard install, and this still happens. I applied the latest diff, cleared cache and the problem removes.
Tagging for an issue summary update.
The question in #12 hasn't been answered in 8 months. So, I testing this on 11.x with and without the link_attribute module. I was not able to reproduce the problem using the steps in the issue summary.
Therefore, closing as cannot reproduce. If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue → starting from "Install Drupal core".
Thanks!
Since no reason for making this change has been given in 7 months, I am closing this issue.
If you agree with change then add a comment explaining why this is needed and reopen the issue, by setting the status to 'Active'.
Thanks!
Time to close this one, per #27.