Open JoeDupuis opened 9 years ago
Hi, I think the branches can be renamed except Master-dev because I still had to verify https://github.com/crossbridge-community/crossbridge/pull/62 - just actually I have no free time to work on this.
Am gonna try to check it out. (Review each change and test it)
as said in #62 I think we should not merge the pull request. I am refactoring a bunch of stuff (http://forum.crossbridge.io/t/new-build-system/22)
I will check is change and merge them with mine manually.
I will proceed with the branch rename then.
Anyway even if we want to accept the pull request, we can merge it by hand. There should be no problem.
I would like to rename a bunch of branch.
Master-dev -> develop (i think master-dev is weird and I am use to see develop branch when following the git flow workflow. I think it's the default name when using the git pluggin)
Also, futures and llvm33 could become feature branches and we might as well use the pluggin default nomenclature "feature/feature-name".
So that would give us : Master-dev -> develop Master futures -> feature/futures llvm33 -> feature/llvm33 master-feature-performance -> feature/performance gh-pages
By using the default nomenclature I think it's less confusing and clean.
Do you see problem with it or I can make the change ?