develooper Front page | perl.perl5.porters | Postings from June 2018

Re: [perl #132671] Bleadperl v5.27.6-206-g16ada235c3 breaksJGAMBLE/Algorithm-QuineMcCluskey-0.16.tar.gz

Thread Previous | Thread Next
Karl Williamson
June 10, 2018 20:11
Re: [perl #132671] Bleadperl v5.27.6-206-g16ada235c3 breaksJGAMBLE/Algorithm-QuineMcCluskey-0.16.tar.gz
Message ID:
On 06/10/2018 11:27 AM, via RT wrote:
> Dana Sun, 10 Jun 2018 08:54:06 -0700, reče:
>> On 06/10/2018 06:45 AM, via RT wrote:
>>>> I fail to see how removing the blocker link causes any loss of
>>>> information as long as the ticket is left open.  Interested parties
>>>> can act on it whenever, well, they take an interest.
>>> In this case possibly interested parties (i.e. the author of the
>>> affected CPAN module) were not informed at all.
>> Shouldn't the module owner automatically be placed in the cc: at
>> ticket
>> creation time?
> Often bleadperl failures are fixed, without the need to tell the module owners.


The argument against this idea is that it may unnecessarily alarm them.

The argument for it is that they are a stakeholder, and should be given 
a heads up about things.  In cases where the problem is too much 
dependence on undocumented/unpromised core behavior, they may well have 
some wisdom to contribute.

In any event, the time to notify them is long before the ticket is 
removed from the blockers list.

The latest that we should notify them, I believe is when the discussion 
in the ticket veers towards the module being part of the problem.  That 
we're not doing, and it requires some conscious effort to do so, so 
can't be relied on.

So I still lean to changing BBC tickets to automatically notify the 
module's maintainers.  Text could be added to this message to quell 
their anxieties.

There could be a short exclude list of authors who we don't notify, 
because past experience has shown them to violate Hanlon's law.

> ---
> via perlbug:  queue: perl5 status: open

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About