which is why my primary suggestion is to have the update center metadata generator create the version labels while it's doing its stuff...
covers the 99% use case... only have hpi plugin goals and/or and IRC bot for those cases where you want to create the version number up front... though the issue there is: "what if you end up never releasing that version?" At least if you only consider already released versions as discovered by the indexing you know those versions were released. On 13 January 2014 16:57, Sandell, Robert <[email protected]>wrote: > I like everything that everyone has said +1! > > One worry though about using the release plugin as the creator of new > versions; since some plugins are "stuck" on old core dependencies they > wouldn't automatically get the new release version feature. So wouldn't it > be better to do it in the backend update center, I guess the effect would > be the same just delayed by 24h? > > Robert Sandell > Software Tools Engineer - SW Environment and Product Configuration > Sony Mobile Communications > > > > -----Original Message----- > > From: [email protected] [mailto:jenkinsci- > > [email protected]] On Behalf Of Jesse Glick > > Sent: den 13 januari 2014 16:24 > > To: [email protected] > > Subject: Re: JIRA "current" version option > > > > 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. > > -- > 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. > -- 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.
