RELEASE.md

This is step-by-step description on how to release new version of CopyQ.

Verify the Builds

• copyq-beta Ubuntu package
• copyq-beta on OBS
• Windows builds

Update Version and Changelog

Update CHANGES.md file.

Bump version.

utils/bump_version.sh 3.3.1

Verify and push the changes.

for r in origin gitlab bitbucket; do git push --follow-tags $r master || break; done

Build Packages

Upload source files for copyq Ubuntu package.

git checkout v3.3.1
utils/debian/create_source_packages.sh
dput ppa:hluk/copyq ../copyq_3.3.1~*.changes

Build on OBS.

osc co home:lukho:copyq
cd home:lukho:copyq/CopyQ-Qt5
./create_beta_package.sh
$EDITOR debian.changelog
osc commit

Update flathub package:

1. Update "tag" and "commit" in "com.github.hluk.copyq.json" file.
2. Push to your fork.
3. Create pull request.
4. Wait for build to finish (flathubbot will add comments).
5. Verify the build.
6. Merge the changes if build is OK.

Publish Release

Download:

• binaries for Windows from AppVeyor

• binary for OS X from github

• source package from github

• OBS packages

  utils/download_obs_packages.sh 3.3.1 1.1
  

Create release on github for the new version tag.

Upload packages and binaries to:

• github

• sourceforge

• fosshub

    ./utils/fosshub.py 3.3.1 $TOKEN
  

Update Homebrew package for OS X.

brew install vitorgalvao/tiny-scripts/cask-repair
brew upgrade cask-repair
cask-repair copyq

Write release announcement to CopyQ group.