[GH-ISSUE #1177] Cypht lifecycle and branches: creation of a 2.x branch #596

Closed
opened 2026-02-25 21:35:28 +03:00 by kerem · 2 comments
Owner

Originally created by @marclaporte on GitHub (Aug 16, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1177

Originally assigned to: @kroky on GitHub.

As per https://github.com/cypht-org/cypht/wiki/Lifecycle

We will do normally do: 2.0.0 > 2.1.0 > 2.2.0 -> 2.3.0
Exceptionally, we may do: 2.0.0 -> 2.0.1 -> 2.1.0 -> 2.2.0 -> 2.3.0

So we should not have a 2.0.x branch, and in instead rename it to 2.x

Originally created by @marclaporte on GitHub (Aug 16, 2024). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1177 Originally assigned to: @kroky on GitHub. As per https://github.com/cypht-org/cypht/wiki/Lifecycle We will do normally do: 2.0.0 > 2.1.0 > 2.2.0 -> 2.3.0 Exceptionally, we may do: 2.0.0 -> 2.0.1 -> 2.1.0 -> 2.2.0 -> 2.3.0 So we should not have a [2.0.x branch](https://github.com/cypht-org/cypht/tree/2.0.x), and in instead rename it to 2.x
kerem closed this issue 2026-02-25 21:35:28 +03:00
Author
Owner

@marclaporte commented on GitHub (Aug 16, 2024):

A note from Victor:

GitHub gives the following commands:

git branch -m 2.0.x 2.x
git fetch origin
git branch -u origin/2.x 2.x
git remote set-head origin -a

Just be sure to change origin to upstream or whatever you use for the GitHub remote you use.

<!-- gh-comment-id:2293519653 --> @marclaporte commented on GitHub (Aug 16, 2024): A note from Victor: GitHub gives the following commands: ``` git branch -m 2.0.x 2.x git fetch origin git branch -u origin/2.x 2.x git remote set-head origin -a ``` Just be sure to change origin to upstream or whatever you use for the GitHub remote you use.
Author
Owner

@marclaporte commented on GitHub (Aug 16, 2024):

https://github.com/cypht-org/cypht/tree/2.x now exists

<!-- gh-comment-id:2293550448 --> @marclaporte commented on GitHub (Aug 16, 2024): https://github.com/cypht-org/cypht/tree/2.x now exists
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#596
No description provided.