|
Packit |
bbb0ff |
---------------------
|
|
Packit |
bbb0ff |
Releasing new version
|
|
Packit |
bbb0ff |
---------------------
|
|
Packit |
bbb0ff |
|
|
Packit |
bbb0ff |
Before release, it is usually worth the time to browse the Bugzilla
|
|
Packit |
bbb0ff |
for patches and easy fixes.
|
|
Packit |
bbb0ff |
|
|
Packit |
bbb0ff |
1) Apply (merge) all changes you want to be present in the new version
|
|
Packit |
bbb0ff |
to the master branch.
|
|
Packit |
bbb0ff |
|
|
Packit |
bbb0ff |
2) Increment the version in the VERSION file (do not forget to commit)
|
|
Packit |
bbb0ff |
|
|
Packit |
bbb0ff |
3) run 'make upstream-release', which will
|
|
Packit |
bbb0ff |
- check if the version in VERSION does not exist already
|
|
Packit |
bbb0ff |
- create a tarball
|
|
Packit |
bbb0ff |
- upload the tarball to fedorahosted.org
|
|
Packit |
bbb0ff |
- tag the current commit with the version tag
|
|
Packit |
bbb0ff |
- push tags upstream
|
|
Packit |
bbb0ff |
|
|
Packit |
bbb0ff |
Note: we track bugs in Fedora / RH QA Process bugzilla for appropriate
|
|
Packit |
bbb0ff |
package, so fixing bugs in upstream release does not constitute
|
|
Packit |
bbb0ff |
an event for any bug status flipping.
|
|
Packit |
bbb0ff |
.
|