- Navigate to https://github.com/mattkae/miracle-wm/releases
- Draft a new release
- Name the tag
v.X.Y.Z
- Title the release
v.X.Y.Z
- Target a branch, most likely
develop
- Describe the release (You may generate release notes, but please make sure that they make sense before doing so)
- Check out the commit that you just released in Step 1
- Bump the version number in
snap/snapcraft.yaml
to theX.Y.Z
- Commit this buumped version
- Next (this part is silly), comment out the
override-pull
of themiracle-wm
part - Run
snapcraft
- Finally, run
snapcraft upload --release=stable ./miracle-wm_*.snap
TODO: Implement #59 to fix the weirdness of this process
- Clone the repo (make sure that the folder is called
miracle-wm
) - Update
debian/changelog
with:- Version
X.Y.Z-distro
(wheredistro
is "noble"") - The same content as you in the Github release
- A correct current timestamp
- Version
- Next:
cd miracle-wm
./tools/publish-ppa.sh <X.Y.Z> <DISTRO>
- Navigate to https://launchpad.net/~matthew-kosarek/+archive/ubuntu/miracle-wm
- Wait for the CI to finish, and the package should be ready
Note that you should rebuild for mantic
and noble
. Follow the instructions to make sure that it uploads.
Before following these steps, make sure that you've at least followed this tutorial.
fkinit
rpmdev-bumpspec -n 0.3.0 -c "Update to 0.3.0" miracle-wm.spec
rpmdev-spectool -g miracle-wm.spec
fedpkg new-sources miracle-wm-0.3.0.tar.gz
fedpkg ci -m "Update to 0.3.0"
fedpkg push && fedpkg build