On Sat, 24 Feb 2018 04:33:59 -0800, demerphq wrote:
> On 24 February 2018 at 01:00, Zefram <zef...@fysh.org> 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.
> > Related to this, I have bumped the versions twice now, meaning two> conceptually related changes have resulted in a jump from 1.45 to> 1.48. Personally I think this is silly as it means there are version> gaps in the CPAN published copies of this code, for instance as far as> I can tell the latest version on CPAN is 1.38.
Again, we don’t need new versions for every commit, just every release.
--
Father Chrysostomos
---
via perlbug: queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=131046