That's exactly why I'm going to try to learn what the process is and take it over if I can
For the point ("subversion") releases of perl there's not so much involved - it's pretty much just a case of building that latest point release and uploading it along with the already-existing C toolchain and libraries.
However, for the once-a-year new "version" release there are tasks to be performed that might not be so trivial - eg:
1) build a new mingw64 port of gcc for inclusion in the package - though 5.32.0 stayed with gcc-8.3.0 (same as 5.30.0);
2) build the latest version of the C libraries that Strawberry provides ... which can be even less trivial when it comes to building the C libraries that ship with the "PDL" build;
3) build the latest versions of the "vendor" modules that Strawberry provides (against the latest versions of the afore-mentioned C libraries, where applicable).
However, by my reckoning it has been 168 days since perl-5.34.0 was released, and it shouldn't take that long to perform these tasks.
I have seen no requests for any help with any of those tasks ... nor any explanation of why it's taking so long.
I can only assume that the major problem is one of apathy.
Cheers,
Rob | [reply] |
> I can only assume that the major problem is one of apathy.
Last time I heard about it, which was at the beginning of October, the new maintainers complained about their unfamiliarity with the ecosystem on IRC. Unfortunately, I don't remember whether it was #perl on Libera.Chat or irc.perl.org; nevertheless, I'd recommend asking there first if you want to help.
map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
| [reply]
[d/l] |
I'd recommend asking there first if you want to help.
I don't do IRC.
Also, I don't claim that "I want to help".
However, if I was aware of some issue that they're facing, with which I beleieved that I might be able to help, then I would most certainly provide that help.
If the issues are all with the operation of the "ecosystem" then that probably counts me out ... though I wonder that they have not yet been able to patch/replace that ecosystem with something that they can work with.
It's likely that the only things I could help them with are:
1) Updating to a later version of the 64-bit and 32-bit gcc toolchains and mingw runtimes - for which I'd just point them to the ready-built toolchains at https://winlibs.com/ that I've been successfully using to build perl and perl extensions for about the last 8 months;
2) Building the C libraries that ship with Strawberry - most of which I've built in the past, and some of which I continue to regularly build;
3) Building problematic "vendor" modules;
4) Building perl itself - though I doubt that's an issue as, these days, perl builds straight out of the box on Windows.
But, AFAICT, they're pretty intent on keeping their cards close to their chests, and that's about all I know.
Cheers,
Rob
| [reply] |