Skip to content
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

Master-dev -> develop #72

Open
JoeDupuis opened this issue Jan 5, 2015 · 3 comments
Open

Master-dev -> develop #72

JoeDupuis opened this issue Jan 5, 2015 · 3 comments

Comments

@JoeDupuis
Copy link
Member

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 ?

@vpmedia
Copy link
Member

vpmedia commented Jan 6, 2015

Hi,
I think the branches can be renamed except Master-dev because I still had to verify #62 - just actually I have no free time to work on this.

@JoeDupuis
Copy link
Member Author

Am gonna try to check it out. (Review each change and test it)

@JoeDupuis
Copy link
Member Author

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.

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

No branches or pull requests

2 participants