Verify parity between 4.x and 7.x-3.x?

Created on 7 June 2023, over 1 year ago
Updated 7 July 2023, about 1 year ago

A lot of our patches get applied to either 4.x (previously 8.x-3.x) or 7.x-3.x, but are never ported to the other, and I suspect the two are out of sync in the way they work.

Example: Handle case of only email before @ returned. And match email via user_load_by_mail, not custom SQL. Downport adjusts the way the user’s email address is matched against the accounts in the database, but it is still very different from the way 4.x does the matching.

I suspect no one is trying to do an upgrade in place to get from core 7.x to 9.x or 10.x, so this may not matter that much, but also I wonder if we have lost anything important since the branches diverged.

📌 Task
Status

Active

Version

4.0

Component

Code

Created by

🇺🇸United States jproctor

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

Comments & Activities

  • Issue created by @jproctor
  • 🇺🇸United States jrglasgow Idaho

    I can tell you that when the 8.x-3.x branch was created, that was te last time that there was any parity between the 7.x branch and the later branches.
    I know there are features I added to the 8.x-3.x branch that I didn't bother backporting to 7.x-3.x.

Production build 0.71.5 2024