Skip to content

Conversation

@stes
Copy link
Member

@stes stes commented Sep 13, 2023

  • Make sure all tests pass on the rc branch. Also make sure that the milestone related to this release is fully done. Move issues that wont make it into the release to the next milestone, then close the milestone.
  • Head to cebra.__init__ and make sure that the __version__ is set correctly.
  • Create a PR between rc and main
  • Tag the PR with the release label.
  • A github action will be run -- if it doesnt start, try removing and re-adding the release label (step 4).
  • Carefully check that the release looks fine --- the version from the PR will be pushed to release-staging and staging in the cebra-internal repo. Note: If you update the PR, these version will not be automatically updated. Repeat step 4 or trigger a manual workflow run if you need to update the staging version
  • If all looks good, tests pass and the PR is reviewed, merge the PR using rebase merging.
  • Delete the branch
  • Checkout the updated main branch, git tag v1.2.3 with the correct format (if alpha/beta tags are used in version, use v1.2.3a4 or v1.2.3b4), and git push v1.2.3 the tag.
  • Pushing the tag will update the release in cebra-internal. The source tree will land on main, the pre-build wheel and source distribution on release.

@stes stes self-assigned this Sep 13, 2023
@cla-bot cla-bot bot added the CLA signed label Sep 13, 2023
@stes stes added the release PR is intended for release to PyPI label Sep 13, 2023
@stes
Copy link
Member Author

stes commented Sep 13, 2023

Released on test pypi: https://test.pypi.org/project/cebra/0.3.0/

@stes
Copy link
Member Author

stes commented Sep 13, 2023

GPU tests on datasets pass:

image

@stes stes requested a review from MMathisLab September 13, 2023 11:53
@stes
Copy link
Member Author

stes commented Sep 13, 2023

Let's potentially wait for one more dataset-related PR from @gonlairo before merging.

@stes stes changed the title Release v0.3.0 Release v0.3.0rc2 Sep 14, 2023
@stes stes removed the release PR is intended for release to PyPI label Sep 14, 2023
@stes stes force-pushed the stes/release-final-0.3.0 branch from a932c7f to 3835520 Compare September 14, 2023 01:17
@stes
Copy link
Member Author

stes commented Sep 14, 2023

Waiting for #69

@stes stes force-pushed the stes/release-final-0.3.0 branch from 3835520 to 9eaaca2 Compare October 3, 2023 11:28
@stes stes force-pushed the stes/release-final-0.3.0 branch from 52eb738 to 173a130 Compare October 3, 2023 16:27
@stes
Copy link
Member Author

stes commented Oct 3, 2023

Added a docker container for testing --- running full test suite now.

@stes stes requested a review from MMathisLab October 6, 2023 16:39
@stes
Copy link
Member Author

stes commented Oct 6, 2023

All tests pass

image

cc @MMathisLab for review

@stes stes added the release PR is intended for release to PyPI label Oct 6, 2023
@stes stes merged commit 0c13a97 into main Oct 6, 2023
@stes stes deleted the stes/release-final-0.3.0 branch October 6, 2023 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA signed release PR is intended for release to PyPI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants