Updated Releasing a new version of Clementine (markdown)
parent
8f68ec6e2b
commit
fa3dbf9998
|
@ -48,9 +48,7 @@ It's usually best to make a release candidate about 1 week before the final rele
|
|||
|
||||
- Gather all the binary and source packages together into one directory on your local machine. Buildbot will put the binary packages you told it to build into http://builds.clementine-player.org/
|
||||
|
||||
- If the set of packages you built was different to the last time we did a release, edit the constants at the top of the `dist/googlecode_upload_all.py` file. For example, you might need to add another Fedora or Ubuntu version. When it's up to date, run that script from the directory you copied all the packages into:
|
||||
|
||||
python ~/src/clementine/dist/googlecode_upload_all.py
|
||||
- [https://github.com/clementine-player/Clementine/releases/new](Create a new release on github) and upload all the packages you downloaded before.
|
||||
|
||||
- Send an email to the mailing list to announce the release candidate. You should include a short summary of the major features and link readers to the full changelog and the downloads page. For example: https://groups.google.com/forum/?fromgroups=#!topic/clementine-player/3jPLPYKVuAU
|
||||
|
||||
|
|
Loading…
Reference in New Issue