Hi Tony, I propose to use following workflow to version logback-contrib: 1) we don't use SNAPSHOT 2) if a version is "in work", it gets the version of the following next release 3) if a release is ready, we tag this version in GIT For example: - Version v_0.1.1 is ready: git tag -a v_0.1.1 - In pom.xml we have version 0.1.2 - many development iterations - Version v_0.1.2 is ready: git tag -a v_0.1.2 ... OK? Christian 2012/12/20 Tony Trinh <tony19@gmail.com>
Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: cdc7faa03d32b37da39e64ba8a10d8a2359d256b
https://github.com/qos-ch/logback-contrib/commit/cdc7faa03d32b37da39e64ba8a1... Author: Tony Trinh <tony19@gmail.com> Date: 2012-12-19 (Wed, 19 Dec 2012)
Changed paths: M pom.xml
Log Message: ----------- Add SNAPSHOT label to version
Commit: 74dca95fb9432f96dae2ef4707ebc44d8885cc81
https://github.com/qos-ch/logback-contrib/commit/74dca95fb9432f96dae2ef4707e... Author: Tony Trinh <tony19@gmail.com> Date: 2012-12-19 (Wed, 19 Dec 2012)
Log Message: ----------- Merge branch 'master' into fixbr
Commit: 082e705d09b557ac69eb77dfc7e6d6f59b31a4ed
https://github.com/qos-ch/logback-contrib/commit/082e705d09b557ac69eb77dfc7e... Author: Tony Trinh <tony19@gmail.com> Date: 2012-12-19 (Wed, 19 Dec 2012)
Changed paths: M eclipse/pom.xml M jackson/pom.xml M json/classic/pom.xml M json/core/pom.xml M json/pom.xml M mongodb/access/pom.xml M mongodb/classic/pom.xml M mongodb/core/pom.xml M mongodb/pom.xml M pom.xml
Log Message: ----------- [maven-release-plugin] prepare release v_0.1.2
Compare: https://github.com/qos-ch/logback-contrib/compare/262b20f15678...082e705d09b...
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev