mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 13:05:53 +03:00
[GH-ISSUE #1177] Cypht lifecycle and branches: creation of a 2.x branch #596
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#596
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@marclaporte commented on GitHub (Aug 16, 2024):
A note from Victor:
GitHub gives the following commands:
Just be sure to change origin to upstream or whatever you use for the GitHub remote you use.
@marclaporte commented on GitHub (Aug 16, 2024):
https://github.com/cypht-org/cypht/tree/2.x now exists