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

CONTRIBUTING documentation suggests features be done against next branch, but they should really be done against 3.0 #1771

Open
itamarst opened this issue Sep 6, 2019 · 2 comments
Open

CONTRIBUTING documentation suggests features be done against next branch, but they should really be done against 3.0 #1771

itamarst opened this issue Sep 6, 2019 · 2 comments
Labels
question

Comments

@itamarst
Copy link

itamarst commented Sep 6, 2019

Probably CONTRIBUTING should be updated with accurate information? Or next should be updated, not sure how the branch model works.
@johann8384
Copy link
Member

Well, we're in a weird spot right now. master is the 2.x release. next is the next 2.x. 3.0 is a near re-write and is completely different. So, if you are working on 3.0, merge to 3.0. If you are enhancing 2.x go to next. @manolama will know more about how enhancements/updates to 2.x might get ported to 3.0.

@JerAxxxxxxx
Copy link

When will the version of opentsdb3.0 be released? When can I download it on the official website?

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

No branches or pull requests
3 participants
@johann8384 @itamarst @JerAxxxxxxx