Branch version numbers - Githubissues

PhileCMS / Phile

A flat file CMS with a swappable parser and template engine.

https://philecms.github.io/

Other

257 stars 49 forks source link

Branch version numbers #99

Closed james2doyle closed 10 years ago

james2doyle commented 10 years ago

We should probably try and find a branch style that works. I personally like the way PyroCMS does it:

2.2/master
2.2/develop
2.3/master
2.3/develop
etc.

In this style, there is no master branch.

This would mean changing from release/1.0.0 to something like 1.0/master. I recently tagged 1.1 because there were quite a few changes since the 1.0 commit. But now the branch is release/1.0.0 but it has a 1.1.0 tag on it. So moving away from that would be nice.

Schlaefer commented 10 years ago

Until the urge for a more complicated solution comes up I propose a simple master branch with tags for releases.

james2doyle commented 10 years ago

Yeah I am leaning that way as well. Thats how I have been managing the release/1.0.0 branch