Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Create a changelog for 0.2.0 #37

dkingofpa opened this Issue May 19, 2012 · 2 comments


None yet
2 participants

Probably just a Changelog text file? Maybe not. Haven't decided yet.

@ghost ghost assigned dkingofpa May 19, 2012


pearcec commented May 22, 2012

Do we merge all of this into master then work on 0.3.0 off of develop?

With git flow, I think we can create a release branch for 0.2.0. After which, we can keep committing post-0.2.0 code to the develop branch. Any changes that are added to the 0.2.0 release branch will automatically get merged back in to develop when the release branch is closed. To be safe though, you can always use feature branches to avoid having to commit to develop.

I think this is how it would work.

@dkingofpa dkingofpa pushed a commit that referenced this issue May 28, 2012

David King [GH-37] Add CHANGELOG.md 21bb77d

@dkingofpa dkingofpa closed this May 28, 2012

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