forked from forgejo/forgejo
[crystal/release] Forgejo v1.18.3-1crystal0 #1
Labels
No Label
bug
duplicate
feature/enhancement
help wanted
invalid/wontfix
question
upstream/Forgejo
upstream/Gitea
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: crystal/forgejo#1
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
I have created this issue to document and track the release process for the next version of my fork, based upon the new version of Forgejo released today. There have been several previous releases of my fork, and I would like to start documenting a consistent and reproducible process for creating these releases.
What I'm building here is effectively a soft-fork of Forgejo, which is in turn a soft-fork of Gitea, with some small additional features backported to the current release branch. This means that, much like Forgejo, I need to regularly archive the current branches and rebase them upon fresh copies of the upstream branches. Previous branches mirrored from upstream such as
forgejo,main, andv1.18/forgejoare typically updated by checking out the respective branch from mirror/forgejo and force pushing to the respective branch in this repo. Alternatively, it can be done by deleting the branch from this repo, checking it out from the upstream repo, and then pushing it to this repository. Archives of these upstream branches are stored in the upstream repository using hidden refs and the varioussoft-fork/*branches, so they are not archived in this repo. Meanwhile, the fork branches such asv1.18/crystalorcrystal/ciwill be moved to a respectivearchive/[date]/[branch]branch and a new branch with the old name is created from the respective upstream branch. Each additional commit that needs to be added to the branch is then cherry-picked, either from the old version of the same branch, or from the relevant upstream commit. Sometimes commits may be squashed or rewritten during this process to reduce the necessary human labor during future rebases.The following tasks must be accomplished for this release:
v1.18/crystalbranchcrystal:v1.18/forgejowithmirror:v1.18/forgejov1.18/crystalanyway.v1.18/crystalbranchv1.18/crystalbranch based onv1.18/forgejov1.18/crystalci-verifystep is not hung.v1.18.3-1crystal0on forgejo-buildThe build has been deployed to CrystalCommit Forge
The release page is available at https://sc.cryxtal.org/crystal/forgejo-build/releases/tag/v1.18.3-1crystal0
That's all folks!