develooper Front page | perl.perl5.porters | Postings from April 2014

RFC: RT handling changes for >= 5.21

Thread Next
From:
Karl Williamson
Date:
April 28, 2014 19:39
Subject:
RFC: RT handling changes for >= 5.21
Message ID:
535EAE74.10501@khwilliamson.com
We have a new status available in RT, "pending release"

Here's how I think we should be using it:

When we fix a bug in blead, we set the ticket to this status instead of 
the current "resolved" status.

RT automatically sends an email to the requester, something like
========================
Thanks for reporting this issue.

This issue is now fixed in the latest Perl development version.  [Words 
might be added to the effect that if you have the time and skills, you 
can download and check it out].

We will send you an email when the fix is in a stable Perl version.
========================

When the stable release is made, someone goes through the tickets with 
this "pending release" status and bulk changes them to resolved, with 
the stable Perl version also set.  I'm hopeful that RT can be set up to 
send a special email when the status changes from pending to resolved 
that says something like

=========================
Thanks for reporting this issue.

This issue is now fixed and a stable Perl containing it is available for 
download at http://foo
=========================

We need to account for other possibilities for resolution, so this 
message should be generated only for this particular transition.

One possibility that doesn't fit with this scenario is if the bug was 
fixed in an earlier Perl version, but there were no TODO tests, so we 
didn't notice it until now.  It would be nice if the resolver would 
indicate in the resolution message the earliest stable Perl version the 
fix is in.

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About