Too many branches

[Zimmi48]

This project has a lot of branches, and this means that it is hard to follow the development. As can be seen in https://github.com/ocaml/dune/branches/all, most of these branches are associated to merged PRs. It would be nice to at least delete these branches. Probably some old and unused branches like dev too. I would personally recommend going further by having contributors open PRs from branches on their forks (including core contributors) but this is your call. Making the number of branches smaller would already be a good improvement.

[rgrinberg]

I don't have any objections to deleting old branches. I did not realize that people followed all the different branches.

[Zimmi48]

I did not realize that people followed all the different branches.

That's not what I meant. I mean that they might want to look at your various branches to try to infer your model of development. For instance, you have a dev branch that has not been used for a long time but can be confusing because people used to the git-flow model might wrongly think that this is the branch that PR should target.

[emillon]

PRs should target master. I'll cleanup the merged branches so that it's less messy!

[emillon]

Done - I also clarified that bit in the contributing guide. Thanks!

[emillon]

(And I'll also try to make my PRs from my fork :))