- Status changed to Closed: duplicate
about 1 year ago 11:08pm 25 September 2023 - 🇺🇸United States tr Cascadia
This is done differently than the proposed patch for the current branch of the module. See ✨ Use HTTP instead of FTP Needs review . I don't want a different implementation in the two branches.
The way issues like this are normally handled in Drupal is to patch the current branch first, then backport that patch to previous versions if there is community interest. We always work on the current branch first, because that way the patch gets into the code going forward - if it is committed to a previous branch first then chances are the changes will remain in the previous branch and the functionality will not make it into the current branch.
So in general we don't have separate issues for the different branches. We fix things in the current branch first and then backport those fixes.
This feature can be implemented in the same way in both branches, with only minor differences (variable vs config) and some minor test changes. Let's get the 2.0.x branch committed first, in ✨ Use HTTP instead of FTP Needs review , then that issue can be set to "Patch "(to be ported)" and the 2.0.x patch can be backported to 7.x-1.x in that issue to ensure the code remains the same in the two branches.