pharo-ide/Calypso

Far too many branches

StephanEggermont opened this issue · 11 comments

Contributing to Calypso is difficult when it is not clear which branch to push to. Please reduce to the absolute minimum

Better would maybe be to have a CONTRIBUTION.md file?

Did you see bold section "Contribution (Pharo 7 and higher)" in readme?

No. Why is there a dev branch?

All development is accumulated in dev branch through PRs. When we decide that it is time for release we push dev to master and create a new release tag. In addition we push (or create) to floating branch (0.16.x for example).
This way master is always stable.

You can propose better process. But honestly I don't have time to spend on it.

Drop dev, do that all in master. No branch that adds no value. Currently, master doesn't.

I think it has value.
For example loading master gives you latest stable release.

No, because there is no such thing. Release for what? Stable is different for 7 and for 8.

Sorry, that’s because I’ve been fighting bad dependency management in Pharo for the past five years or so, and this exact problem cost a client of mine about 30 man months two years ago.

I work with master and dev branch on projects that have more than 75 dependencies without problem from that kind of management. For me the problem does not comes from there.

It just creates extra work and confusion. The absolute number of dependencies is only a small part of it. On which branches should Pharo 7 and 8 depend?