Put in instructions for getting release-0.3 instead of master

[IainNZ]

Wording can almost surely be improved, so feel free to change it directly instead of merging this PR.

Just wanted to put something in there to discourage people doing builds on master then complaining about packages being broken.

[StefanKarpinski]

We could change things so that release-0.3 is the default branch. That would make it so that cloning and doing make gives people something that they should be using, which may be a good idea.

[IainNZ]

That was definitely something that crossed my mind, but wasn't sure how much buy in there'd be for that. Would we switch back to master-default when we get to 0.4-pre stage?

[StefanKarpinski]

Yeah, just make the default branch at any point in time the one that we recommend people use. That seems like a pretty sane thing to do :-)

[ivarne]

Would that make it tedious to ensure that pull requests are suggested against master? Currently it is quite a few clicks to create a PR against release-0.3.

Changing default for git clone is not as problematic as I thought when I wrote that mailing list post now that I think of it.

[StefanKarpinski]

It is unfortunate that you can't separately change the default branch for cloning and the default branch for PRs and such. Or at least you can't that I know of.

[garborg]

Pardon my ignorance, but if someone clones Julia and repeatedly pulls &
makes, will the version change under their noses? Not saying that'd be
reason not to do it, but it seems that would break code unexpectedly if
true.

On Thu, Oct 9, 2014 at 12:22 PM, Ivar Nesje [email protected]
wrote:

Would that make it tedious to ensure that pull requests are suggested
against master? Currently it is quite a few clicks to create a PR against
release-0.3.

Changing default for git clone is not as problematic as I thought when I
wrote that mailing list post now that I think of it.

—
Reply to this email directly or view it on GitHub
#8642 (comment).

[StefanKarpinski]

No, it doesn't work like that – it's just the default branch that is initially checked out upon cloning.

[garborg]

OK, thanks.

[staticfloat]

I wish Github would just automatically open a PR against the branch that is closest to your proposed merge's branch. I just emailed them about it to get it on their radar. :P

[ivarne]

But until we find out how to make PR against a master more convenient with release-0.3 as default, I think this PR is an improvement. Should we just merge it?

[pao]

Even if the default is changed, this isn't wrong.