develooper Front page | perl.perl5.porters | Postings from June 2009

Re: Perl 5.10.1

Thread Previous | Thread Next
Craig A. Berry
June 23, 2009 13:00
Re: Perl 5.10.1
Message ID:
On Tue, Jun 23, 2009 at 2:03 PM, Aristotle Pagaltzis<> wrote:
> * Craig A. Berry <> [2009-06-22 06:23]:
>>  even if it were possible to release 5.10.0 + 1
>> regression fix and call it 5.10.1, you would fix one regression
>> but potentially cause dozens or hundreds of others for anyone
>> upgrading from 5.8.9 to this hypothetical 5.10.1. I don't think
>> upgrading should cause you to lose bug fixes you previously had
>> -- that kind of negates the meaning of the word "upgrade."
> I cannot follow. Until such time as any 5.10.1 is released, the
> upgrade path from 5.8.9 is 5.10.0. Surely this upgrade path also
> causes loss of bug fixes that 5.8.9 contains? So why would
> someone who has upgraded to 5.8.9 but is holding off on 5.10.0
> not have the option of holding off on 5.10.1 also? If there is no
> reason, then why would these users be of any concern to when
> determining the admissible state of a 5.10.1 release? Surely the
> users who are currently using unpatched 5.10.0 perls are of much
> greater concern to that question?

You're right to point out that there is already a less than ideal
situation for someone on 5.8.9 wanting to upgrade to 5.10.x.  But at
least 5.8.9 came out *after* 5.10.0, so it doesn't utterly defy
expectation that it would have some things that were not in a 5.10.x
release yet.  But if 5.10.1 were to come out now without many of the
optimizations and bug fixes in 5.8.9, I think that would really
confuse people. Even if they don't follow development closely enough
to regard what's merged into the maint-5.10 branch as an indication of
what's going to be in the next 5.10.x release, they would be rightly
disappointed if the newest version in the current branch were in some
ways an upgrade and other ways a downgrade compared to the older

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About