Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reminder: Update py39cloud branch with next release #229

Closed
jdblischak opened this issue Nov 19, 2024 · 3 comments · Fixed by #239
Closed

Reminder: Update py39cloud branch with next release #229

jdblischak opened this issue Nov 19, 2024 · 3 comments · Fixed by #239
Assignees

Comments

@jdblischak
Copy link
Collaborator

Note to self: with the next release of TileDB-SOMA, we need to update main as well as the branch py39cloud

We will only need to maintain the separate py39cloud branch for as long as we continue to maintain the py39 TileDB Cloud env. Hopefully the transition to py312 will not be protracted (and thus it's not worth updating our release guidelines)

cc: @johnkerl

@jdblischak jdblischak self-assigned this Nov 19, 2024
@jdblischak
Copy link
Collaborator Author

@johnkerl reminder that we can't forget this step. When you open the update PR for 1.15.0 to merge into main, then I'll adapt your PR and submit one to the branch py39cloud

@johnkerl johnkerl changed the title Reminder: update py39cloud branch with next release Reminder: Update py39cloud branch with next release Dec 17, 2024
@johnkerl
Copy link
Collaborator

johnkerl commented Dec 17, 2024

and thus it's not worth updating our release guidelines

I need to document what I do for as long as I have to do it -- this is why I have the release procedure -- I'll update it right now

@jdblischak
Copy link
Collaborator Author

Closed by #239 (GitHub only auto-closes an Issue when its linked PR is merged into main)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants