Releases

Policy

• 1 release per month, at first 10 days of month
• Every release has to have associated milestone
• Not completed issues moved to next release milestone

Release checklist

1. Start and complete test run with Release plan at Worklog Reminder Qase project
2. Create and push git tag with version name: v1.0.0
3. Build packages for all platforms
   1. Linux: deb, rpm, zip
   2. MacOS: dmg, zip
   3. Windows: exe
4. Upload artifacts to new Github Release
   1. You can use GITHUB_TOKEN=$GITHUB_TOKEN yarn run publish to automatically upload artifacts
   2. Pre-built artifacts available at Github Actions
5. Rename assets according the list bellow:
   1. worklog-reminder.amd64.deb
   2. worklog-reminder.x86_64.rpm
   3. Worklog.Reminder-linux-x64.zip
   4. worklog-reminder.dmg
   5. Worklog.Reminder-darwin-x64.zip
   6. Worklog.Reminder.Setup.exe
6. Fill description with a list of completed issues in release milestone.
   1. Issue links must be provided at the end of each line
7. Publish Linux package:
   1. For Debian/Ubuntu
   2. For RPM-based
8. Publish release! Users will be notified about new version from 0 to 15 minutes

Release to Debian/Ubuntu

1. Rename deb package to worklog-reminder-${VERSION}.${ARCH}.deb
   1. For example worklog-reminder-1.0.0-beta.4.amd64.deb
2. Upload package to https://cloudsmith.io/~doka-nt/repos/worklog-reminder/packages/
   1. Or use CLI TOOL cloudsmith push deb doka-nt/worklog-reminder/any-distro/any-version worklog-reminder-1.0.0-beta.4.amd64.deb
3. Users will get update as soon as they run apt-get update && apt-get upgrade worklog-reminder

Release to RPM-based Linux

1. Upload package to https://cloudsmith.io/~doka-nt/repos/worklog-reminder/packages/
   1. Fedora: cloudsmith push rpm doka-nt/worklog-reminder/fedora/any-version worklog-reminder-1.0.0.x86_64.rpm
   2. OpenSuse: cloudsmith push rpm doka-nt/worklog-reminder/opensuse/any-version worklog-reminder-1.0.0.x86_64.rpm
2. Users will get update as soon as they run yum update