default branch "develop" can be painful for consumers about cf-deployment HOT 5 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/140335063

The labels on this github issue will be updated when the story is started.

from cf-deployment.

@robdimsdale I think you have a good point, that people expect to be able to clone a repo and start using it.

I think part of the issue is that we want different default branches for "consuming" and "producing" -- the former would be master and the latter would be develop. Unfortunately, there's no github feature for setting different defaults for git clone and PRs (or even more interesting, git clone git@... and git clone https://...)

Anyway, it probably makes the most sense to go with master, since more and more people are moving into the "consumer" category. I'll let @anEXPer chime in if he has an opinion.

from cf-deployment.

I think we've probably reached the point in the life of this repo that we should switch it the default branch for consumers, rather than for contributors. We can message about making PRs from develop in the readme and potentially elsewhere.

Let's change the default branch to master.

from cf-deployment.

I've changed the default to master.

from cf-deployment.

Excellent, thanks all.

from cf-deployment.