How would the workflow change? I.e. what state transitions will be added/removed?
> On 01.07.2016, at 00:39, James Dumay <[email protected]> wrote: > > Hi all, > > Blue Ocean had previously had an "In Review" state in JIRA to track which > changes are in development but are ready for review as a PR when we had these > tickets in a private JIRA. > > The developers working on Blue Ocean would like to introduce it again so we > have a more accurate state for where each other's work is at. For the design > work the In Review state means that a design is "ready enough" (proposed, > rather than just spitballing) to receive input from the wider community. In > that last case we would be using this status to facilitate feedback on UX > with the community. > > Would there be any objections to adding this to the JENKINS project's JIRA > workflow? There should be minimal/no impact for other users. > > Request is being tracked on https://issues.jenkins-ci.org/browse/INFRA-802 > > Thanks, > James > > -- > 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/96ed51c5-dd8c-4090-8723-3bc226c04c20%40googlegroups.com. > 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/930CD661-8F0D-4E46-A916-EFF70BDAC7BA%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
