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

Remove branch master? #177

Closed
NiteshKant opened this issue Oct 22, 2016 · 6 comments
Closed

Remove branch master? #177

NiteshKant opened this issue Oct 22, 2016 · 6 comments
Labels

Comments

@NiteshKant
Copy link
Contributor

Code from current master is in branch 0.2.x and the next version code is in branch 0.5.x.

IMO, the existence of a branch named master is sort of confusing when we are working on two different versions. So, should we delete master branch and just have two 0.2.x and 0.5.x branches?

After deletion of master, 0.2.x will be the default branch till 0.5.x is stable.

@ktoso
Copy link
Contributor

ktoso commented Oct 22, 2016

Sure, I don't mind.
At this phase of the project we don't have any strong guarantees about compatibility anyway do we?
Just want to make sure we use the same meanings for the version numbers :)

@NiteshKant
Copy link
Contributor Author

@ktoso yep there are no strong compatibility guarantees.

Just want to make sure we use the same meanings for the version numbers

The current versioning scheme sounds ok to you?

@yschimke
Copy link
Member

@NiteshKant will travis build both new master branches?

@NiteshKant
Copy link
Contributor Author

@yschimke I would say once, 0.5.x is ready for release, we would no longer require 0.2.x.
Assuming we update all related projects (tck and cli) with 0.5.x's first release, is there a reason we would need to build both?

@yschimke
Copy link
Member

Probably not, just assumes that 0.2.x is complete, and 0.5.x is close to ready. No issue from me.

@NiteshKant
Copy link
Contributor Author

Removed master branch. Thanks guys!

ilayaperumalg pushed a commit to ilayaperumalg/rsocket-java that referenced this issue Dec 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants