Created on 9 April 2025, about 1 month ago

Problem/Motivation

Hi, just wondered that the latest merges went into 2.x while 2.0.0 is based on 2.0.x and 2.x is not shown on the project page.

That might lead to confusion. Is this intentional?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ’¬ Support request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

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

Comments & Activities

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

    We're switching to a new pattern for release naming; we'll settle this up ASAP.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Thank you rszrama :)

  • πŸ‡ΊπŸ‡ΈUnited States TomTech

    To be clear, we should NOT have created the 2.0.x branch initially.

    We should have just created the 2.x branch. Unfortunately, it isn't possible to delete branches once they have been created.

    2.x is the default branch, and all new issues should target this branch.

    There is no way to "force" 2.x on the project page. Once we tag a 2.1.0 release, though, that should resolve that issue.

    (And for completeness, we might have needed to create a 2.0.x branch in the future, in a specific scenario...but don't expect that to be the norm.)

Production build 0.71.5 2024