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

Readme links need updated for new repo location #112

Closed
CreativeNotice opened this issue Feb 21, 2015 · 3 comments
Closed

Readme links need updated for new repo location #112

CreativeNotice opened this issue Feb 21, 2015 · 3 comments

Comments

@CreativeNotice
Copy link
Member

No description provided.

@DannyCork
Copy link
Contributor

closed and merged pull request automatically (by accident!)

@deanlaw
Copy link
Contributor

deanlaw commented Mar 2, 2015

Should this update also be added to the development branch? Also, for my own clarification, should we be working on these issues in the development branch first and then merge them with the master branch? Sorry if the question sounds ignorant, but I just want to make sure that when I am able to contribute, that I am following the right workflow.

@CreativeNotice
Copy link
Member Author

Dean, I think that's up to you. It would be interesting to work in http://semver.org/. Perhaps non-breaking bug fixes and features are pulled right into master but breaking features are released in another branch (maybe dev) for review before being merged to master.

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

No branches or pull requests

3 participants