Skip to content
This repository has been archived by the owner on May 25, 2022. It is now read-only.

branches clarification #37

Open
sensorario opened this issue May 30, 2019 · 5 comments
Open

branches clarification #37

sensorario opened this issue May 30, 2019 · 5 comments

Comments

@sensorario
Copy link
Collaborator

Are master old version (1.x) and develop next version (2.0)?

@davidedantonio
Copy link
Owner

yep

@sensorario
Copy link
Collaborator Author

May I suggest different names like master as always the next version and 1.0 (for example) for all LTS? Whenever master is complete, ... we should create branch 2.0, tag 2.0.0 in the same place and master will be the develop of next version: 2.1 or 3.0.

@davidedantonio
Copy link
Owner

It's a good idea for me!
Do you think we have to deal with it now or can we do it after the release of version 2.0?

@sensorario
Copy link
Collaborator Author

I'll start now if possibile.

@davidedantonio
Copy link
Owner

Sure, no problem for me!

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

No branches or pull requests

2 participants