Skip to content

v6 as master, feature freeze of v5 #1533

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

Closed
angularsen opened this issue Apr 11, 2025 · 2 comments · Fixed by #1536
Closed

v6 as master, feature freeze of v5 #1533

angularsen opened this issue Apr 11, 2025 · 2 comments · Fixed by #1536
Milestone

Comments

@angularsen
Copy link
Owner

angularsen commented Apr 11, 2025

@lipchev I'm thinking we should make v6 our master branch now. Thoughts?

Mainly to get new pull requests and discussions for the v6 code base and not v5. Also to get more momentum on stabilizing and finalizing v6 so we can ship it.

Units can still be backported to a maintenance/v5 branch.

@lipchev
Copy link
Collaborator

lipchev commented Apr 11, 2025

Yeah, sorry it's been a busy week- I had a lot of things planned as a follow-up to #1507 but haven't gotten around to it... (when I do, there will be tons of momentum 😃 )

Making release/v6 the default branch would make it a little easier to contribute (that damn Sync feature would finally work directly from the web-interface).

I don't know if there are any gotchas- you're the git expert..

@angularsen
Copy link
Owner Author

Closed by #1536

@angularsen angularsen added this to the v6 milestone Apr 11, 2025
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