proposal: remove "opportunity to carry out other desirable work" from the Exceptional Cases considerations in the blocker bug SOP

[Matthew Miller]

In https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases, 
there is a list of factors we may consider when dealing with last minute or
difficult to resolve blockers. One item on the list is:

* Whether delaying the release may give us an opportunity to carry out other desirable
work

I would like to remove this from the list, and perhaps go so far as to include it
as something we _shouldn't_ consider.

There is always an infinite amount of desirable work, and it's tempting to
push the schedule just to get one more thing in. But! Admiral Ackbar meme
gif! that temptation is a trap! Any such additional work increases the risk
of further delay, and actually pushes off getting all the other work that
*did* make the release from getting to users.

If something isn't ready, there is always the next release, and often there
is the possibility of providing whatever other desirable work via an update
-- or through an alternate module stream after the the release.

What do you think? Reasonable? Thanks!

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Harold Dost]

Are there any examples where it might have been cited I the past?
If so, maybe narrow the definition to things which would result in a less
buggy release.

Otherwise +1 from my perspective.

On Wed 21 Oct 2020 at 20:07, Matthew Miller <mattdm(a)fedoraproject.org&gt;
wrote:

>  In
>  https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases,
>
>  there is a list of factors we may consider when dealing with last minute or
>  difficult to resolve blockers. One item on the list is:
>
>  * Whether delaying the release may give us an opportunity to carry out
>  other desirable work
>
>  I would like to remove this from the list, and perhaps go so far as to
>  include it
>  as something we _shouldn't_ consider.
>
>  There is always an infinite amount of desirable work, and it's tempting to
>  push the schedule just to get one more thing in. But! Admiral Ackbar meme
>  gif! that temptation is a trap! Any such additional work increases the risk
>  of further delay, and actually pushes off getting all the other work that
>  *did* make the release from getting to users.
>
>  If something isn't ready, there is always the next release, and often there
>  is the possibility of providing whatever other desirable work via an update
>  -- or through an alternate module stream after the the release.
>
>  What do you think? Reasonable? Thanks!
>
>  --
>  Matthew Miller
>  <mattdm(a)fedoraproject.org&gt;
>  Fedora Project Leader
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  
-- 

________________________________________

*Harold Dost* | @hdost

[Jaap Bosman]

Agree with Matthew, becauseThe Perfect is the enemy of the good.

On 22-10-2020 09:29, Harold Dost wrote:
>  Are there any examples where it might have been cited I the past?
>  If so, maybe narrow the definition to things which would result in a 
>  less buggy release.
>
>  Otherwise +1 from my perspective.
>
>  On Wed 21 Oct 2020 at 20:07, Matthew Miller <mattdm(a)fedoraproject.org 
>  <mailto:[e-mail]>> wrote:
>
>      In
>      https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases
>      <https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cas...;,
>
>      there is a list of factors we may consider when dealing with last
>      minute or
>      difficult to resolve blockers. One item on the list is:
>
>      * Whether delaying the release may give us an opportunity to carry
>      out other desirable work
>
>      I would like to remove this from the list, and perhaps go so far
>      as to include it
>      as something we _shouldn't_ consider.
>
>      There is always an infinite amount of desirable work, and it's
>      tempting to
>      push the schedule just to get one more thing in. But! Admiral
>      Ackbar meme
>      gif! that temptation is a trap! Any such additional work increases
>      the risk
>      of further delay, and actually pushes off getting all the other
>      work that
>      *did* make the release from getting to users.
>
>      If something isn't ready, there is always the next release, and
>      often there
>      is the possibility of providing whatever other desirable work via
>      an update
>      -- or through an alternate module stream after the the release.
>
>      What do you think? Reasonable? Thanks!
>
>      -- 
>      Matthew Miller
>      <mattdm(a)fedoraproject.org <mailto:[e-mail]>>
>      Fedora Project Leader
>      _______________________________________________
>      test mailing list -- test(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>      To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>      Fedora Code of Conduct:
>      https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>      <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>      List Guidelines:
>      https://fedoraproject.org/wiki/Mailing_list_guidelines
>      <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>      List Archives:
>      https://lists.fedoraproject.org/archives/list/[e-mail]
>      <https://lists.fedoraproject.org/archives/list/[e-mail]...
>
>  -- 
>
>  ________________________________________
>
>  *Harold Dost* | @hdost
>
>
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

[Sudhir D]

+1 to the proposal.

On 10/21/20 11:37 PM, Matthew Miller wrote:
>  In
> https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases,
>  there is a list of factors we may consider when dealing with last minute or
>  difficult to resolve blockers. One item on the list is:
>
>  * Whether delaying the release may give us an opportunity to carry out other desirable
> work
>
>  I would like to remove this from the list, and perhaps go so far as to include it
>  as something we _shouldn't_ consider.
>
>  There is always an infinite amount of desirable work, and it's tempting to
>  push the schedule just to get one more thing in. But! Admiral Ackbar meme
>  gif! that temptation is a trap! Any such additional work increases the risk
>  of further delay, and actually pushes off getting all the other work that
>  *did* make the release from getting to users.
>
>  If something isn't ready, there is always the next release, and often there
>  is the possibility of providing whatever other desirable work via an update
>  -- or through an alternate module stream after the the release.
>
>  What do you think? Reasonable? Thanks!
>