github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[proposal] Create a RC1 for 1.2.0 and release/v1.2 branch #975

New Issue
Closed
opened 2025-11-02 03:43:56 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2025-11-02 03:43:56 -06:00
Owner
Copy Link

Originally created by @sapk on GitHub (Aug 18, 2017).

We could create the release/v1.2 branch and pre-release a rc1. We could continue work on future release on master and backport fix for 1.2.0 final version?

These would ease the process of the final release by fixing the changes and keep work to get done in master.

Originally created by @sapk on GitHub (Aug 18, 2017). We could create the release/v1.2 branch and pre-release a rc1. We could continue work on future release on master and backport fix for 1.2.0 final version? These would ease the process of the final release by fixing the changes and keep work to get done in master.
GiteaMirror added the type/proposal label 2025-11-02 03:43:56 -06:00
GiteaMirror commented 2025-11-02 03:43:57 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 18, 2017):

Sound reasonable. Any idea? @bkcsoft @appleboy @andreynering @lafriks

@lunny commented on GitHub (Aug 18, 2017): Sound reasonable. Any idea? @bkcsoft @appleboy @andreynering @lafriks
GiteaMirror commented 2025-11-02 03:43:57 -06:00
Author
Owner
Copy Link

@appleboy commented on GitHub (Aug 19, 2017):

LGTM.

@appleboy commented on GitHub (Aug 19, 2017): LGTM.
GiteaMirror commented 2025-11-02 03:43:57 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Aug 19, 2017):

Yeah, we'd end up "backporting" to the stable-branch (RC2 etc), but it might help with getting stable releases out more often

@bkcsoft commented on GitHub (Aug 19, 2017): Yeah, we'd end up "backporting" to the stable-branch (RC2 etc), but it might help with getting stable releases out more often
GiteaMirror commented 2025-11-02 03:43:57 -06:00
Author
Owner
Copy Link

@lcges commented on GitHub (Aug 21, 2017):

I think so too.
I already see that future version 1.3 will have the same end as current version 1.2
This is a solution to current and future problems.

@lcges commented on GitHub (Aug 21, 2017): I think so too. I already see that future version 1.3 will have the same end as current version 1.2 This is a solution to current and future problems.
GiteaMirror commented 2025-11-02 03:43:57 -06:00
Author
Owner
Copy Link

@lcges commented on GitHub (Aug 21, 2017):

My proposal for future development is:

  • Adding a few changes to the new version (currently too many changes, because there are so many bugs)
  • Frequent issuing large version (1.1, 1.2, 1.3 ...)
  • Milestones close in up to 200 issues
  • Bug fixes to version (x.x.1, x.x.2, x.x.3 ...)

A few things are already well run. But you need to improve product releases.

I invite you to open discussion and give your solution.

P.S. Thanks to all creator and co-creator for such a heavy and good project! Together we can do more!

@lcges commented on GitHub (Aug 21, 2017): My proposal for future development is: * Adding a few changes to the new version (currently too many changes, because there are so many bugs) * Frequent issuing large version (1.1, 1.2, 1.3 ...) * Milestones close in up to 200 issues * Bug fixes to version (x.x.1, x.x.2, x.x.3 ...) A few things are already well run. But you need to improve product releases. I invite you to open discussion and give your solution. P.S. Thanks to all creator and co-creator for such a heavy and good project! Together we can do more!
GiteaMirror commented 2025-11-02 03:43:58 -06:00
Author
Owner
Copy Link

@sapk commented on GitHub (Aug 21, 2017):

Releasing more often large version also limit the work of backport.

We could also start thinking of v2 and what breaking change we would like to do. (allready have some here : https://github.com/go-gitea/gitea/milestone/5)

@sapk commented on GitHub (Aug 21, 2017): Releasing more often large version also limit the work of backport. We could also start thinking of v2 and what breaking change we would like to do. (allready have some here : https://github.com/go-gitea/gitea/milestone/5)
GiteaMirror commented 2025-11-02 03:43:58 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 23, 2017):

branch release/v1.2 has been created.

@lunny commented on GitHub (Aug 23, 2017): branch release/v1.2 has been created.
GiteaMirror commented 2025-11-02 03:43:58 -06:00
Author
Owner
Copy Link

@sapk commented on GitHub (Aug 23, 2017):

@lunny thx

@sapk commented on GitHub (Aug 23, 2017): @lunny thx
GiteaMirror commented 2025-11-02 03:43:58 -06:00
Author
Owner
Copy Link

@ptman commented on GitHub (Aug 31, 2017):

So the branch and rc1 have been made? Is this done?

@ptman commented on GitHub (Aug 31, 2017): So the branch and rc1 have been made? Is this done?
GiteaMirror commented 2025-11-02 03:43:58 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 31, 2017):

Yes, you are right!

@lunny commented on GitHub (Aug 31, 2017): Yes, you are right!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#975
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?