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
Apply Git workflow: GitFlow #18
Comments
Conclusion post sent to soci-users under RFC Apply Git branching model thread: On 3 March 2013 01:40, Mateusz Loskot mateusz@loskot.net wrote:
After reading Pro Git book and Git manual, followed by kernel Git workflow The actual development happens in topic branches. Things can potentially get broken in the integration branch, but mustn't in the master branch. I aim to follow this well-known, well-tested and common approach: the GitFlow
This naming is not possible as once we add 'release' branch, |
Using GitFlow With GitHub is a really good introduction to GitFlow for GitHub users with The Poster where all the basics are displayed. If you use SourceTree, check Smart branching with SourceTree and Git-flow |
I've just made first step and applied the GitFlow scheme to the repository:
Here are the three basic rules:
If you like it, use gitflow software as it really makes the process simple. There is lots of good readings about GitFlow as it has become de facto a standard for software rolling cycles of traditional releases. However, I will wrap up basic info on the Flow, so contributors will be displayed with name of GitFlow and at least know they should branch off from develop. |
I consider it's happened. Should any new issues be discussed, either reopen this or open new issue or post to the mailing lists. |
This task discusses Git workflow that is aimed to be applied before releasing next SOCI , either bugfix release for 3.1.0, or new features release SOCI 4.0.0.
At the moment, SOCI development history is flat and there is no easy way to apply bug fixes to existing releases, thus no easy way to issue bug fix releases.
There are two popular Git workflows:
In GitHub Flow article, Scott Chacon says:
I think, git-flow is the right choice for SOCI. It is simple and based on use of two branches only: master and develop, where in fact, on daily basis, only develop branch is used.
What I look for is a dead simple, clear, safe,well structured Git workflow with the following features:
I also requested for comments on soci-users in Apply Git branching model thread.
Please, feel encouraged to post your comments on this topic.
The text was updated successfully, but these errors were encountered: