> Am 14.08.2017 um 17:10 schrieb Oleg Nenashev <[email protected]>:
> 
> IIUC this proposal would allow us to have an intermediate state between In 
> Review and Resolved/Fixed.
> 

That makes our workflow complex to understand for others. Who is responsible to 
move the issues from the new state to resolved? If you consider to add another 
state please make it optional and do not change the default (and simple) 
workflow for plugin authors.

> Exactly
> 
> +1, I have seen people get confused when an issue is moved to
> Resolved/Fixed after a PR is merged yet the fix is not available on
> the update center.
> 
> Good point. Once we have the fix, we will be able to update Jenkins Issue 
> autoupdater to move the
> issues to the "Stage Release" state instead of "Resolved".

Please do not change the current behavior. Most plugin authors do not need such 
an overly complex workflow. We just fix some issues, make a release and move 
forward to the next ones.

> 
> (BTW I am not sure what the Closed resolution is for.)
> 
> Nobody knows :(
> Maybe we want to just remove it and merge with Resolved
> 
> 
> 2017-08-14 17:07 GMT+02:00 Jesse Glick <[email protected] 
> <mailto:[email protected]>>:
> +1, I have seen people get confused when an issue is moved to
> Resolved/Fixed after a PR is merged yet the fix is not available on
> the update center. IIUC this proposal would allow us to have an
> intermediate state between In Review and Resolved/Fixed.
> 
> (BTW I am not sure what the Closed resolution is for.)
> 
> --
> 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 
> <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] 
> <mailto:jenkinsci-dev%[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3BF8cn17%2Bs_5dAHzfK_%3DewW7B%3D0vSGGSiWfE_fBpGwew%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3BF8cn17%2Bs_5dAHzfK_%3DewW7B%3D0vSGGSiWfE_fBpGwew%40mail.gmail.com>.
> For more options, visit https://groups.google.com/d/optout 
> <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] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAx%2B8oN8dBU4a59PbrEp8ZnO_YFWBcgB2Y48uOV06_FUw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAx%2B8oN8dBU4a59PbrEp8ZnO_YFWBcgB2Y48uOV06_FUw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/BB00F70F-2A41-40B5-84A2-61E427F49969%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to