Re: "defer-next-dev" label ignored; why?

Hi James,

I was helping BooK with prep for the release this morning; this was an
oversight on both our parts, sorry.

I think commit d676f771e06c3e7fd4d32d61fafcdcb00999517d should be reverted.

To reduce the risk of this sort of error in the future, I added to our
current release notes document to update the Release Manager's Guide
"Dual-life CPAN module synchronisation" section to check for existing PRs
for modules that might be tagged as "defer-next-dev".

Sincerely,
Eric




On Fri, 17 Apr 2026 at 13:10, James E Keenan <[email protected]> wrote:

> @Book,
>
> Updating my local checkout of blead this morning, I saw this commit:
> ```
> commit d676f771e06c3e7fd4d32d61fafcdcb00999517d (HEAD -> blead,
> origin/blead, origin/HEAD)
> Author:     Philippe Bruhat (BooK) <[email protected]>
> AuthorDate: Fri Apr 17 11:23:01 2026 +0200
> Commit:     Philippe Bruhat (BooK) <[email protected]>
> CommitDate: Fri Apr 17 11:23:01 2026 +0200
>
>      update JSON::PP from CPAN to 4.18
>
>      4.18 2026-03-20
>          - fix duplicate specification warning (GH#93, 88; Heiko Jansen++)
>          - fix typo (GH#92, sobrado8086++; GH#96, Grinnz++)
>          - fix decode_json prototype (reported by bdfoy++)
>          - fix space_after (GH#89, haukex++)
>
>      4.17_01 2023-07-29
>          - fix a reentrant issue (experimental) (GH#61, 87)
>
>      Co-authored-by: Eric Herman <[email protected]>
> ```
> I was surprised to see this, because in
> https://github.com/Perl/perl5/pull/24331, where I had done the work
> needed to merge this module into blead, we agreed that it introduced
> changes in code behavior too late in the current dev cycle to risk that
> merging.  I self-assigned the ticket and marked it "defer-next-dev."  If
> you disagreed with that designation, you could have said so in that
> ticket before proceeding with d676f771e0.  Can you explain?
>