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.

Sign up for GitHub

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

Jump to bottom

Clarify branches #336

Open
ryantm opened this issue Nov 13, 2023 · 2 comments
Open

Clarify branches #336

ryantm opened this issue Nov 13, 2023 · 2 comments

Comments

@ryantm
Copy link
Contributor

ryantm commented Nov 13, 2023

It looks like development work is now being done on the branch called release-0.11.0 not to be confused with tag v0.11.0. Is this expected? Based on the README, I expected unstable to be the branch getting the latest updates.

Only use unstable for developing with the latest features. PR's against old releases can be accepted but no active support will be done. The default branch for this repo is updated whenever a new release tag is made. Only specific release branches are "stable."
@psionic-k
Copy link
Member

I had to update release quite a bit to leave it in a reasonable state before doing other work. Didn't finish looking at unstable's remaining unmerged changes. More important to move forward in other directions. If you need anything critical, I added support information in that last update.

@psionic-k
Copy link
Member

psionic-k commented Nov 15, 2023 •
edited

Haha, sorry, wrong Repo. It's late. Deleted last message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ryantm @psionic-k