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

Implement proper branch management #44

Closed
RubenVerborgh opened this issue Dec 5, 2016 · 6 comments
Closed

Implement proper branch management #44

RubenVerborgh opened this issue Dec 5, 2016 · 6 comments
Assignees
@RubenVerborgh
Milestone
v1.2.0

Comments

@RubenVerborgh
Copy link
Member

RubenVerborgh commented Dec 5, 2016 •
edited
Loading

Bugs such as LinkedDataFragments/Client.js#26 (comment) occur because people use the latest master as opposed to the latest release.

Proposal A (vote with 👍 )

  • develop becomes the branch were development happens
  • master always points to the latest release (which we tag)

Proposal B (vote with 😄 )

  • stable becomes the default branch
@mielvds
Copy link
Member

mielvds commented Dec 6, 2016

Wasn't Proposal A not already the case?

@mielvds
Copy link
Member

mielvds commented Dec 6, 2016

Ah nevermind, I got confused with repos

@RubenVerborgh
Copy link
Member Author

Given the 4 votes, this is settled. To be implemented starting with the next release.

@mielvds mielvds added this to the Early 2017 milestone Dec 9, 2016
@mielvds
Copy link
Member

mielvds commented Dec 9, 2016

I've created a Milestone for the next release to organize things. We should have this biannual.

@RubenVerborgh RubenVerborgh mentioned this issue Jan 10, 2017
Closed
@mielvds
Copy link
Member

mielvds commented Jan 11, 2017

@RubenVerborgh you feel like making this change?

@RubenVerborgh RubenVerborgh self-assigned this Jan 11, 2017
@RubenVerborgh
Copy link
Member Author

Done. Development on develop from now on; next commit on master is release.

@RubenVerborgh RubenVerborgh mentioned this issue Jan 16, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RubenVerborgh RubenVerborgh

Labels
None yet
Projects
None yet
Milestone
v1.2.0
Development

No branches or pull requests
2 participants
@RubenVerborgh @mielvds