Merge 2.2.x and 2.x branches

Created on 22 April 2025, 4 days ago

Problem/Motivation

Currently, the 2.2.x and 2.x development branches each have recent enhancements separately applied. Some were applied to one development branch, while one was applied to the other.

Steps to reproduce

Visit the below comparisons to see the current set of differences in each direction.

Proposed resolution

Since the current release 2.2.6 and any current release plans don't seem to need to support multiple feature releases, merge 2.2.x into 2.x and only supply and work from the one development branch: 2.x.

Remaining tasks

  • Merge 2.2.x into 2.x.
  • Ensure any open tickets and merge requests are updated to point to 2.x.
  • Delete the 2.2.x branch.
πŸ“Œ Task
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States jcandan

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

Comments & Activities

  • Issue created by @jcandan
  • πŸ‡ΊπŸ‡ΈUnited States jcandan

    No merge required. It turns out that, although the 2.2.x to 2.x comparison shows the logo change as a difference, the logo change is indeed part of 2.2.x.

    The 2.2.x is the most up-to-date branch.

    We can safely rebase 2.x from 2.2.x, then remove 2.2.x.

    Maintainer may find the following helpful.

    git fetch --all
    git checkout --track origin/2.x
    # skipped previously applied commit 8fb5e79, reapply-cherry-picks to include skipped commits.
    git rebase --reapply-cherry-picks 2.2.x
    # see that the branches now match at HEAD.
    git log
    # delete remote branch.
    git push origin :2.2.x
    # delete local branch.
    git branch -D 2.2.x
    
Production build 0.71.5 2024