Tagging a released version

eko / FeedBundle

A Symfony bundle to build RSS feeds from your entities

http://vincent.composieux.fr

MIT License

141 stars 50 forks source link

Tagging a released version #17

Closed dbu closed 11 years ago

dbu commented 11 years ago

Once dev-zend is merged into master, do you think it will become possible to tag a released version in the near future (like next month)? we plan to tag stable releases of the cmf bundles in march, once symfony 2.2 became stable. the more dependencies provide tagged versions, the easier for us to model the dependencies.

igorw commented 11 years ago

Seconded. Also, please add a branch-alias.

eko commented 11 years ago

Hi, A stable tag is available since this morning :)

igorw commented 11 years ago

You need to tag a version number like v1.0.0.

dbu commented 11 years ago

1.0.0 (without the v) would work as well.

the concept of semantic versioning composer uses is

if you just added new features without any impact on the existing features break, raise the 3rd number, like 1.0.1
if you have changes that can have minor influence on existing client code, change the middle number, like 1.1.0
after a complete refactor where you moved classes and namespaces and the application model, you up the first number, so you would go to 2.0.0

the long of this is explained here: http://semver.org/

eko commented 11 years ago

Thank your for this really interesting reading!

I will now use this way to tag my versions number, I've created the 1.0.0 tag.