On Sun, Jan 12, 2014 at 4:18 PM, Ulli Hafner <[email protected]> wrote: > [some sufficiently authenticated way to] create a new version for a developer > to plan the next > release (status is ‚Unreleased‘), and another command to release that version
Sounds like a lot of overhead for developers. IMHO anything like this should be done automatically as part of the Maven release process, which has all of that information. But creating a version label after a release has been performed seems much more important, and probably sufficient. If we had a field for fix version, you could set fixed issues to that version when writing up the changelog for a release (which is currently a manual process anyway, in the wiki). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
