Brother,

Myself, I am just starting to learn git.
I agree that the the master (default) branch should be the release channel. I think it would be easier for people unfamiliar with git (I know how it feels). I agree that the dev version should be on it's own branch, and that as a (somewhat potential) developer, this would not cause me a problem.

This way, the default branch would basically hold the version history and anyone who wants the main version can more easily find what they are looking for.

Of course, that's my invaluable 2 cents...

On 3/15/2015 1:44 PM, Br. Samuel Springuel wrote:
Henry's post mentioned that master is the default branch in git. That got me thinking that if we put the official releases on their own branches, then the user would have to specifically check out that branch to install. That's an extra step for users who may not be really comfortable with git (or on the command line). Despite the fact that it's more complicated, perhaps something more like the following would be better:

- master: all releases are on this branch, tagged appropriately. The only changes made specifically on this branch are bug fixes which affect the most recent stable version. - develop: all code changes are merged to this branch. It represents the cutting edge of development.

When we decide we're going to make a release, we make a new branch for the beta (kind of like I suggested in what Élie quoted). Once we're ready to go official, then this branch is merged into master and we tag the master with the new release number. The beta branch would then be deleted (not the commit history, just the branch identifier).

This is a bit more complicated (two long lived branches instead of one), but it eliminates the need to check out a branch to install the stable version after a git clone command. Would that make life easier for you, the users? If you were a potential (or current) developer, would this level of complication intimidate you?

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)

PAX ☧ ΧΡΙΣΤΟΣ

_______________________________________________
Gregorio-users mailing list
Gregorio-users@gna.org
https://mail.gna.org/listinfo/gregorio-users


_______________________________________________
Gregorio-users mailing list
Gregorio-users@gna.org
https://mail.gna.org/listinfo/gregorio-users

Reply via email to