Skip to content

Commit

Permalink
fix instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
MisterTea committed May 1, 2024
1 parent 9a50ecb commit 1483b77
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions docs/creating_release.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,10 @@
6. `git add external_imported` and commit/push any changes
7. Create a github release using the latest commit and tag it with `et-vA.B.C` where A/B/C is the major/minor/patch version.
8. Switch to the deployment branch
9. Copy id_rsa / id_rsa.pub / .gnupg to the deploymen directory. The rsa key needs to have write access to the debian-et github repo and the gnupg key needs to have write access to launchpad
9. Build and run a docker image interactively from ubuntu.Dockerfile
10. inside the docker image, run deploy_ubuntu_ppa.sh
11. Exit the docker image and create a vagrant VM for debian
12. inside the vagrant vm, run build_all_deb.sh
13. Follow the instructions at the end of the build_all_deb command to push the new debian artifacts. Do not push the dbgsym (debug symbols) because github cannot handle files that large
9. Edit the `deployment/debian_SOURCE/changelog` file and add a entry for the new release.
10. Copy id_rsa / id_rsa.pub / .gnupg to the deploymen directory. The rsa key needs to have write access to the debian-et github repo and the gnupg key needs to have write access to launchpad
11. Build and run a docker image interactively from ubuntu.Dockerfile
12. inside the docker image, run deploy_ubuntu_ppa.sh
13. Exit the docker image and create a vagrant VM for debian
14. inside the vagrant vm, run build_all_deb.sh
15. Follow the instructions at the end of the build_all_deb command to push the new debian artifacts. Do not push the dbgsym (debug symbols) because github cannot handle files that large

0 comments on commit 1483b77

Please sign in to comment.