Mailing List Archive

PSC #102: 2023-03-R24
Hi,

Today, the three of us convened again.

Topics discussed:

* Bug reporting by email: we commit to nothing as an organisation. Some
would-be submitters of issues don't want to use GitHub. They can just
send an email to perl5-porters and hope that some helpful soul will
copy-paste to GitHub. We encourage the conventional use of GitHub.
* On the topic email bug reports, it's likely time to deprecate perlbug
as a way to send bug reports. It could be updated to point the user to
GitHub, and to print perl -V output (etc.) to copy and paste. We
should also have a better set of templates for issues on GitHub.
* The segfaults on feature-class and refaliasing won't be fixed before
5.38, and should just be documented as "known bugs"
* After we discussed renaming RFC to PPC, the general sentiment seemed
to be "in favor", so we're going to make the rename
* Rik volunteered to release 5.38, we still need a release manager
for 5.37.11
* Some discussions about preparing the Perl Toolchain Summit plans
(which will host the first ever in-person PSC meeting)

--
Philippe Bruhat (BooK)

Treat those you outrank well... you never know when they will outrank you.
(Moral from Groo #7 (Image))
Re: PSC #102: 2023-03-R24 [ In reply to ]
On 2023-03-24 5:03 p.m., Philippe Bruhat (BooK) wrote:
> * On the topic email bug reports, it's likely time to deprecate perlbug
> as a way to send bug reports. It could be updated to point the user to
> GitHub, and to print perl -V output (etc.) to copy and paste. We
> should also have a better set of templates for issues on GitHub.

Is this something that's going to be implemented for 5.38, that perlbug will no
longer send emails and just print out the message? In theory its simple and
non-invasive enough, just deletion of non-core functionality. Or is there a
reason for 5.38 to behave the old way? -- Darren Duncan