Front page | perl.perl5.porters |
Postings from June 2020
Re: Announcing Perl 7
From: Karen Etheridge
June 25, 2020 16:34
Re: Announcing Perl 7
Message ID: CAPJsHfBtcR-yqXkFyYbgbvBatDMghE6824oY6f82hb-t_f1MSA@mail.gmail.com
I also want to go on record that I don't disagree with the idea of perl 7
*on principle*; it is certainly a worthy PR exercise if nothing else, as
the attention received outside our normal community is showing. This could
certainly revitalize the idea of Perl as worthy of developer attention in
the modern age.
On Wed, Jun 24, 2020 at 1:49 PM Sawyer X <email@example.com> wrote:
> * Perl 7.0.0 will be the first release. It will effectively be 5.32.0
> with a small number of pragmas (at the very least, strict and warnings)
> features. The goal is to make it as trivial as possible to upgrade from
> 5.32.0 to 7.0.0.
I strongly disagree. We should continue with 5.33.x development (using
the existing version numbering) until (at least) 5.34.0, with the goal of
re-versioning *5.34.0* as 7.0.0. To release 5.32.0 as 7 would be a mistake
for many reasons, not least of which that the feature list is not finalized
and there has been little to no testing, of which we need a ton. I can
think of many many different things that need to be smoketested in various
combinations. This is an important release and must be treated with care.
There is also a growing backlog of fixes waiting to be committed to blead,
which I note is *still* not unfrozen from the 5.32.0 release (which hasn't
had its final steps completed either, e.g. the committing of an epigraph,
ticking off of the release, and the switching back from "stable" to
"development" status in numerous config files).
> * We intend to release 7.0.0 within a year.
So we certainly need development releases before then, so 5.32.0 *cannot
possibly* be renumbered as 7.0.0.
> However, I am setting the goal of releasing it before the end of this
"it will be done by Christmas" is repeating history so hard I have a
concussion. Please let's not do this again.
> There is *a lot* to figure out at this point.
I strongly agree. That's why we can't rush to putting out a 7.0 release
before doing a *lot* of work first.