> > It would be awesome if the issue updater could fill in the correct value > by extracting the Pom version.
I could try to do it (download POM, read version, remove "-SNAPSHOT") in the issue updater, but it presumes that the plugin version does not change. But yes, it could be helpful. - CONS: It's a common case when 4.2-SNAPSHOT gets changed to 4.1.1-SNAPSHOT by the maintainer before the release in order to ship a hotfix. In such case the "Released As" field may be incorrect. - In such case the plugin maintainer would have to manually update tickets Ideally we could add a maven release watcher, which updates the fields after the release by scanning commit history. It's something doable, but I'd guess we would be reimplementing an already existing Maven <Whatever> Changelog plugin engine. Machine-readable and auto-generated changelogs would be a valiant goal for us, because we could use the data in Plugin Site/Update Manager. But it's far beyond the JIRA update proposal. BR, Oleg 2017-08-15 12:55 GMT+02:00 Ulli Hafner <[email protected]>: > > Am 14.08.2017 um 11:45 schrieb Oleg Nenashev <[email protected]>: > > Hi all, > > As a Jenkins user and contributor, I sometimes have difficulties when I > need to understand in which release the fix is available. GitHub commit > links from the bot help much, but it requires extra time to navigate across > commits and UI. In Jenkins core, Remoting and my plugins I would like to > make it more explicit: > > I propose to... > > 1. Modify workflow in the JENKINS project: > - Add a "Stage Release" state (or whatever similar name) > - Instead of "In Progress" => "Resolved", contributors can move > integrated fixed into the "Stage Release" state. > - It may be helpful for components which do not release the > integrated fixes immediately (e.g. Core, its modules, Remoting, Stapler, > Blue Ocean, other plugins) > 2. Add an optional "Released As" field to JIRA (type=String) > - When a contributor moves the issue to "Stage release", "Resolved" > or "Closed" state, an optional field appears in the dialog > - If the field is non-empty, it will appear in the ticket header, > hence users won't need to look into comments and commit histories > > It would be awesome if the issue updater could fill in the correct value > by extracting the Pom version. > > This proposal could improve contributor and user experience, but the > proposed change is opt-in. > > It does not make the field/state mandatory, hence the existing flows won't > be affected if the maintainers do not want to spend time on JIRA updates. > > > WDYT? > > > Thanks in advance, > > Oleg > > -- > 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]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/521bcc90-6ab0-42ec-b6b6-aeb6c225e901% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/521bcc90-6ab0-42ec-b6b6-aeb6c225e901%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jenkinsci-dev/wzc4VLplHvs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/710C9068-A180-4F72-8CCA-6F27D09287F5%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/710C9068-A180-4F72-8CCA-6F27D09287F5%40gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDDS7u8XPyZSBK0Aw%2BUqEpMDwbkCOFei4gLi5ZkcTCEdA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
