From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: perl 5.32
Date: Mon, 21 Dec 2020 16:46:43 -0500 [thread overview]
Message-ID: <fd6b0edf-a04d-bd39-2ceb-ae277b2163cb@cornell.edu> (raw)
In-Reply-To: <87r1ni6gvz.fsf@Rainer.invalid>
On 12/21/2020 3:30 PM, Achim Gratz wrote:
> Achim Gratz writes:
>> I've checked again, there was talk about getting 5.32.1 going end of
>> November but nothing happened since then (on the mailing list anyway).
>> I think it's unlikely to get released this year since Big Sur has
>> created a bunch of problems that they'll probably want to get on top of
>> before collecting the backporting patches.
>
> The current indication is that this release wqill be ready mid to end
> of January.
>
>> I'll see to get 5.32.0 out for you as a test release (let me know which
>> distributions you need in addtion to perl itself). Whether we patch
>> Biber back to 5.30 compatibility or wait for the 5.32.1 update for Biber
>> remains to be decided later on I'd say.
>
> I've cleaned up the patches so they still apply on top of 5.32.0 where
> applicable and built the initial packages. For the rest I'll have to
> set up one of my old build machines as I don't want to move my main
> build box from the official state (which would mean I could no longer
> update other packages).
Great. Thanks for working on this.
Ken
next prev parent reply other threads:[~2020-12-21 21:46 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 23:19 Ken Brown
2020-12-08 19:05 ` Achim Gratz
2020-12-08 23:32 ` Ken Brown
2020-12-09 18:30 ` Achim Gratz
2020-12-09 18:57 ` Achim Gratz
2020-12-09 20:01 ` Ken Brown
2020-12-09 20:37 ` Achim Gratz
2020-12-09 22:33 ` Ken Brown
2020-12-21 20:30 ` Achim Gratz
2020-12-21 21:46 ` Ken Brown [this message]
2020-12-25 19:52 ` Achim Gratz
2020-12-26 17:43 ` Achim Gratz
2020-12-26 23:27 ` Ken Brown
2020-12-27 6:41 ` Achim Gratz
2020-12-27 14:20 ` Ken Brown
2020-12-27 17:10 ` Achim Gratz
2021-01-10 12:42 ` Achim Gratz
2021-01-11 17:55 ` Ken Brown
2021-01-23 15:51 ` [Attn. Maintainers] perl-5.32 Achim Gratz
2021-01-25 20:15 ` Achim Gratz
2021-02-02 19:40 ` [Attn. Maintainers] prepare your packages for release of perl-5.32 Achim Gratz
2021-02-02 22:09 ` Ken Brown
2021-02-03 6:13 ` ASSI
2021-02-03 7:31 ` Marco Atzeri
2021-02-03 13:29 ` Ken Brown
2021-02-04 12:10 ` Andrew Schulman
2021-02-04 14:04 ` Ken Brown
2021-02-04 17:36 ` Ken Brown
2021-02-04 18:08 ` Achim Gratz
2021-02-05 16:36 ` Andrew Schulman
2021-02-07 8:37 ` Achim Gratz
2021-02-08 16:44 ` Andrew Schulman
2021-02-08 21:30 ` Achim Gratz
2021-02-15 20:29 ` Achim Gratz
2021-02-17 22:58 ` Andrew Schulman
2021-02-06 16:13 ` Achim Gratz
2021-02-06 16:59 ` Ken Brown
2021-02-06 19:07 ` Marco Atzeri
2021-02-06 19:19 ` Achim Gratz
2021-02-07 8:05 ` Alexey Sokolov
2021-02-07 8:35 ` Achim Gratz
2021-02-07 9:33 ` Marco Atzeri
2021-06-06 9:01 ` Alexey Sokolov
2021-06-06 17:36 ` Marco Atzeri
2021-02-07 8:54 ` Achim Gratz
2021-02-07 18:12 ` Marco Atzeri
2021-02-09 12:00 ` marco atzeri
2021-02-10 6:03 ` ASSI
2021-02-11 6:38 ` Marco Atzeri
2021-02-09 22:32 ` Lemures Lemniscati
2021-02-10 6:02 ` ASSI
2021-02-11 21:31 ` Jon Turney
2021-02-12 6:46 ` ASSI
2021-02-12 13:09 ` Ken Brown
2021-02-12 15:07 ` Jon Turney
2021-02-13 7:09 ` Marco Atzeri
2021-02-14 8:35 ` Marco Atzeri
2021-02-15 20:33 ` Achim Gratz
2021-02-16 6:11 ` Marco Atzeri
2021-02-15 20:32 ` Achim Gratz
2021-02-15 21:18 ` Ken Brown
2021-02-15 20:31 ` Achim Gratz
2021-02-15 22:39 ` Lemures Lemniscati
2021-03-06 14:42 ` Jari Aalto
2021-03-06 15:31 ` Achim Gratz
2021-02-10 17:01 ` Jon Turney
2021-02-10 19:16 ` Achim Gratz
2021-02-11 17:04 ` Jon Turney
2021-02-11 17:44 ` ASSI
2021-04-09 14:45 ` Jon Turney
2021-04-09 15:58 ` ASSI
2021-04-14 17:16 ` Jon Turney
2021-04-14 18:15 ` Achim Gratz
2022-02-20 14:41 ` Jon Turney
2022-02-27 20:31 ` Marco Atzeri
2021-02-07 18:02 ` Achim Gratz
2021-02-06 20:54 ` perl 5.32 Marco Atzeri
2021-02-07 7:14 ` ASSI
2021-02-07 9:01 ` Marco Atzeri
2021-02-07 9:19 ` Achim Gratz
2021-02-07 12:04 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd6b0edf-a04d-bd39-2ceb-ae277b2163cb@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).