Skip to content

Commit

Permalink
ET 6.2.9
Browse files Browse the repository at this point in the history
  • Loading branch information
MisterTea committed May 1, 2024
1 parent 65c1fb4 commit 9a50ecb
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 1 deletion.
2 changes: 1 addition & 1 deletion CMakeLists.txt
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ endif()
message(STATUS "VCPKG TRIPLET: ${VCPKG_TARGET_TRIPLET}")

# Don't specify languages yet in case we need to bump the cmake version
project(EternalTCP VERSION 6.2.8 LANGUAGES NONE)
project(EternalTCP VERSION 6.2.9 LANGUAGES NONE)

enable_language(C)
enable_language(CXX)
Expand Down
16 changes: 16 additions & 0 deletions docs/creating_release.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Instructions to creating a new ET Release

1. Increment the project(...) version in CMakeLists.txt and push to master.
2. Switch to the release branch
3. Pull in the lastest changes: `git merge master`

Check failure on line 5 in docs/creating_release.md

View workflow job for this annotation

GitHub Actions / Check for spelling errors

lastest ==> latest, last
4. Run `git submodule update --recursive --init` to ensure that the submodules are updated to the latest master/release commit.
5. Run `import_submodules.sh` to create an in-repo copy of the submodules
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

0 comments on commit 9a50ecb

Please sign in to comment.