+1 I've spent a ton of time sifting through blame or repo tags, and this could also be useful for features/API updates too. At the least adding the `Released As` field would suffice
On Monday, August 14, 2017 at 5:45:08 AM UTC-4, Oleg Nenashev wrote: > > 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 > > 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/d31157fe-e9f6-4a1e-a046-c7b93de60f0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
