hi carsten, looks like the right time for discussions about this topic.
the step-list you pointed to, gives a good overview of what has to be done during the release-process. points that come to my mind are: - scm-abstraction that allows to update, commit, branch, tag against most common scm (git, svn) - snapshot-handling - manage state transitions in the project-workspace (replace snapshot-dependencys, increment revision-id) - manage state transitions of artifacts (qa -> production) one important thing that seems not to be adressed by the maven-release-process: patches, quick-fixes. gradle will be a solid ground for a customizable release-process. it should not be to difficult, to setup a first shot release-plugin on base of todays gradle. maybe one that addresses git only. have a nice day -- View this message in context: http://www.nabble.com/Functionallity-a%27la-maven-release-plugin--tp25802972p25814601.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
