Skip to content

Managing wfdb-python branches #34

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

Closed
tompollard opened this issue Jan 3, 2017 · 1 comment
Closed

Managing wfdb-python branches #34

tompollard opened this issue Jan 3, 2017 · 1 comment

Comments

@tompollard
Copy link
Member

I think the plan for this repository was for the master branch to reflect the current release of the package (currently 0.1.2), with developments being merged into a branch with the name of the next release (currently 0.1.3-dev).

The master and dev branches have become out of sync, so I'll merge the master branch into the dev branch. To help avoid conflicts, my preference is for future development work to be done in project specific branches and then merged into the dev branch when ready.

@tompollard
Copy link
Member Author

the master and 0.1.3-dev branches are now in sync

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

No branches or pull requests

1 participant