bonndan / release-manager Goto Github PK

This looks just like another tool I was looking at: https://github.com/liip/RMT

Is this some kind of fork/clone? Is that other repository a fork/clone? It seems to have more following, but this project has more recent updates. Not sure which to try out yet.

Once composer supports custom commands (see composer/composer#2059) the RMT executable should be removed in favor of using composer directly.

https://getcomposer.org/doc/articles/plugins.md

RMT-flow failed with version-persister "vcs-tag"

Finishing a release failed

• file updated had not been committed
• tagging failed (see below)

fatal: Konnte '0.1.0' nicht als gültige Referenz auflösen.
Tagging failed. Please run finish again to retry.
[Liip\RMT\Exception]
Error while executing git command: git flow release finish -F -m "..." 0.1.0

VCS-Commit is automatically added by gitflowCommand as post-release action. However, if there is nothing to commit the action must fail gracefully instead of terminating the process.

Action that executes a configured test command like "phpunit"

RMT finish should ask if the master branch should be publish after having finished the release.

autoload": {
"psr-0": {
"SubStore": "library",
"empty": [
"library",
"library/AAA/BBB"
]
}
},

Needs to be

if (preg_match('/Version\s\d+.\d+.\d+\s-/', $line)){

If there is nothing to commit, RMT finish can fail. Also, tagging should not be done manually. Hence the configuration needs to be checked.

"RMT flow-release" should handle git flow releases:

1. ask for the version (as usual)
2. invoke "git flow release start [version]" with the next version number
3. Proceed with the usual commands (create changelog, etc.)
4. Use the tag message as release description or vice versa
5. make a release
6. invoke "git flow release finish [version]"

Using a different version persister than vcs-based (e.g. composer) causes the changelog formatter to break. Changelog info is retrieved by executing "git log ..." for instance, but no all versions are necessarily present as tag in the vcs.

The changelog is currently stored in an error-prone format and should rather be kept as XML file. Human-readable transformations can be created easily via XLST, PHP or else.

Example:

<changelog>
  <version version="0.3.0" date="2012-07-11">
  <title>My Version</title>
  <commit hash="bidf9u34r...">The commit message</commit>
  </version>

</changelog>

New repos should be handled gracefully.