yves
/
rclone
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

build: instructions on how to make a point release

s3-about
Nick Craig-Wood 2018-09-07 17:10:29 +01:00
parent 820d2a7149
commit 87d4e32a6b
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
RELEASE.md
View File

@ -23,7 +23,6 @@ Making a release
* make upload_website
* make upload_github
* make startdev
* run bin/tidy-beta <previous version> to tidy old betas
* # announce with forum post, twitter post, G+ post
Early in the next release cycle update the vendored dependencies
@ -32,3 +31,25 @@ Early in the next release cycle update the vendored dependencies
* git status
* git add new files
* git commit -a -v
Making a point release. If rclone needs a point release due to some
horrendous bug, then
* git branch v1.XX v1.XX-fixes
* git cherry-pick any fixes
* Test (see above)
* make NEW_TAG=v1.XX.1 tag
* edit docs/content/changelog.md
* make TAG=v1.43.1 doc
* git commit -a -v -m "Version v1.XX.1"
* git tag -d -v1.XX.1
* git tag -s -m "Version v1.XX.1" v1.XX.1
* git push --tags -u origin v1.XX-fixes
* make BRANCH_PATH= TAG=v1.43.1 fetch_binaries
* make TAG=v1.43.1 tarball
* make TAG=v1.43.1 sign_upload
* make TAG=v1.43.1 check_sign
* make TAG=v1.43.1 upload
* make TAG=v1.43.1 upload_website
* make TAG=v1.43.1 upload_github
* NB this overwrites the current beta so after the release, rebuild the last travis build
* Announce!