Re: [Newsletter] Re: [LOG4NET] gitflow

2017-05-22 Thread Dominik Psenner
Right now I could use the develop branch because I have made the modifications that remove the old solution files and updates the solution to visual studio 2015. It makes no sense to make those changes either in the feature branch, nore the master branch but I would like to push those changes somew

Re: [Newsletter] Re: [LOG4NET] gitflow

2017-05-22 Thread Matt Sicker
The master branch holding only production tags is useful for making a production hotfix release. For example, this would be useful in making security patches. As for holding release branches, in my use of git-flow, I've always deleted them after merging back to develop&master, but in theory, it cou

Antwort: [Newsletter] Re: [LOG4NET] gitflow

2017-05-22 Thread Jonas . Baehr
Hi Gary Gregory wrote on 19.05.2017 23:01:10: > Howdy, > > Thank you for the link. > > This is fine until you want to manage more than once major version in one > repo, right? > > Over at HttpComponents, we have decided for now to keep to one repo, as > opposed to one repo per major version.