Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add HOWTO for releasing Gitea #5054

Merged
merged 3 commits into from
Oct 9, 2018
Merged

Add HOWTO for releasing Gitea #5054

merged 3 commits into from
Oct 9, 2018

Conversation

techknowlogick
Copy link
Member

Used instructions from: #2609 (comment)

These are the current steps, as discussed in other PR this process can be changed, however it is important to at least have the current process documented.

@techknowlogick techknowlogick added the type/docs This PR mainly updates/creates documentation label Oct 9, 2018
CONTRIBUTING.md Outdated
* After your PR reviewed and merged, and CI passed, add a tag as `git tag -s -F release.notes v$vmaj.$vmin.$`, release.notes file could be a temporory file to only include the changelog this version which you added to `CHANGELOG.md`.
* And then push the tag as `git push origin v$vmaj.$vmin.$`. Drone CI will automatically created a release and upload all the compiled binary. (But currently it didn't add the release notes automatically. Maybe we should fix that.)
* Send PR for changelog on branch `master`.
* Send PR to https://github.com/go-gitea/blog announcing the release.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- Send PR to https://github.com/go-gitea/blog announcing the release.
+ Send PR to [blog repository](https://github.com/go-gitea/blog) announcing the release.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for suggestion 😄. I've updated PR.

@bkcsoft bkcsoft added lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Oct 9, 2018
@bkcsoft bkcsoft added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Oct 9, 2018
@codecov-io
Copy link

codecov-io commented Oct 9, 2018

Codecov Report

Merging #5054 into master will increase coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5054      +/-   ##
==========================================
+ Coverage    37.4%   37.42%   +0.02%     
==========================================
  Files         306      306              
  Lines       45374    45374              
==========================================
+ Hits        16970    16983      +13     
+ Misses      25950    25941       -9     
+ Partials     2454     2450       -4
Impacted Files Coverage Δ
models/repo_list.go 62.94% <0%> (+1.17%) ⬆️
models/repo_indexer.go 54.23% <0%> (+4.66%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f44d066...1d93263. Read the comment docs.

@bkcsoft bkcsoft added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Oct 9, 2018
@lafriks lafriks merged commit 1ecf92a into go-gitea:master Oct 9, 2018
@techknowlogick techknowlogick deleted the techknowlogick-patch-10 branch February 15, 2019 06:16
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants