develooper Front page | perl.perl5.porters | Postings from February 2018

Re: [perl #131046] [PATCH] Carp: Do not crash when reading @DB::args

Thread Previous | Thread Next
February 25, 2018 10:19
Re: [perl #131046] [PATCH] Carp: Do not crash when reading @DB::args
Message ID:
On 24 February 2018 at 16:39, Father Chrysostomos via RT
<> wrote:
> On Sat, 24 Feb 2018 04:33:59 -0800, demerphq wrote:
>> On 24 February 2018 at 01:00, Zefram <> wrote:
>> > Bonus problem: the patch desynchronises the version numbers of Carp
>> > and
>> > Carp::Heavy, giving the former an unjustified underscored version.
>> /This/ point we need to debate. :-)
>> I believe that every distinct code state of a module in dist/ should
>> have a distinct version number.
> Every commit?  Or just every release?
>> I also believe that minor changes in dist modules during the lifetime
>> of a dev version should be marked as a "dev" versions, and that only
>> prior to release should we bump them to a "non-dev" version. I believe
>> that others have felt the same way in at least some cases as Carp has
>> code to defend against dev/underbar versions.
> That puts a burden on perl maintainers to remember which version scheme to use in each case.  I seem to remember it was Ricardo Signes that ruled that upstream-blead modules should not have underscores in their versions.  That makes things much simpler for me, at least.

This just came up in another context for me. Doesnt this policy just
move the burden around? Who is responsible for bumping the version
then? The first person to change the file in a given release? The RM?
It still seems to me that a version bump every patch is the sanest way
to deal with this stuff while at the same time not externalizing the
costs of the version updates onto someone else...


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