Dear Friends (and Enemies) of version.pm -
As you may already be aware, we are on a push to get Perl 5.10.1 out the door.
In support of this, I have updated the version.pm code in both Module::Build and
core Perl (and which has been pulled into maint-5.10). This is primarily an API
rewrite (renam
On Wed, Jul 15, 2009 at 6:15 AM, John Peacock <
john.peac...@havurah-software.org> wrote:
> If you want to help, the files are here:
>
> https://svn.perl.org/modules/version/trunk/lib/version.pod
>
> and
>
> https://svn.perl.org/modules/version/trunk/lib/version/Internals.pod
>
> or you can just
> Short of handing out commit bits, would it make sense to throw them on a
> wiki page somewhere and let people iterate?
How about I push out 0.76_04 and we use the annotate pages on annoCPAN?
http://www.annocpan.org/~JPEACOCK/version-0.76_03/lib/version.pod
http://www.annocpan.org/~JPEACOCK/vers
On Wed, Jul 15, 2009 at 7:21 AM, John Peacock <
john.peac...@havurah-software.org> wrote:
> > Short of handing out commit bits, would it make sense to throw them on a
> > wiki page somewhere and let people iterate?
>
> How about I push out 0.76_04 and we use the annotate pages on annoCPAN?
>
> htt
David Golden wrote:
I'll take a cut later today and you can incorporate it directly into a
0.76_04 release or put it on a wiki (e.g., the QA wiki). I do tend to
think you'll get better quality edits via a wiki.
I don't have a wiki anywhere that I could use for this (which is why I
suggested
On Wed, Jul 15, 2009 at 10:05 AM, John Peacock <
john.peac...@havurah-software.org> wrote:
> David Golden wrote:
>
>> I'll take a cut later today and you can incorporate it directly into a
>> 0.76_04 release or put it on a wiki (e.g., the QA wiki). I do tend to think
>> you'll get better quality
On Wed, Jul 15, 2009 at 10:13 AM, David Golden wrote:
>
> Easiest is just to park it on the QA wiki, I think. Maybe hang it off the
> toolchain roadmap page?
>
A copy of my edits is attached and I've put a copy on the QA Wiki:
http://perl-qa.hexten.net/wiki/index.php/Version_POD
My goal with
Gisle Aas wrote:
I would suggest that you bump the version number of version to 1.00 so
that becomes the recommended minimal number instead of an arbitrary
number like 0.77; making the recommended invocation:
use version 1.00; $our $VERSION = qw("v1.2.3");
You do know that the above does
>>> I would suggest that you bump the version number of version to 1.00 so that
>>> becomes the recommended minimal number instead of an arbitrary number like
>>> 0.77; making the recommended invocation:
>>> use version 1.00; $our $VERSION = qw("v1.2.3");
+1 on version bump since the API is ch
On Wed, Jul 15, 2009 at 5:35 PM, Gisle Aas wrote:
> I think the term "dotted-decimal" is pretty confusing, especially when what
> you contrast that with is "decimal version numbers" (which includes a dot).
> I suggest you call it "integers separated by dots" or "dotted-integers" for
> short.
+1 f
On Wed, Jul 15, 2009 at 5:50 PM, Gisle Aas wrote:
> We obviously disagree about what makes code readable.
Let me rephrase -- I think putting "use version" last means it's more
likely that someone will inadvertently leave it off. Putting it first
indicates that it's an important precursor, which i
Gisle Aas wrote:
> I think the term "dotted-decimal" is pretty confusing, especially when
> what you contrast that with is "decimal version numbers" (which includes
> a dot). I suggest you call it "integers separated by dots" or
> "dotted-integers" for short.
They used to be fevered to as "numeri
# from David Golden
# on Wednesday 15 July 2009 14:53:
>> our $VERSION = do { use version 1.00; version->declare("v1.2.3")
>> };
>
>I almost hate to say it, but I actually kind of like that. It's
>really, really clear in the intent.
I'm going to keep doing what I've been doing:
our $VERSION
Eric's VCfs has been ported to git, at least more than enough to make
CPDK::Publish, the release tool, work. There's one hard coded use of svn in
CPDK::Publish->check_version_control that should be changed to use
VCfs->status which I'll leave to Eric.
So that's the technical roadblock to moving t
I would suggest that you bump the version number of version to 1.00 so
that becomes the recommended minimal number instead of an arbitrary
number like 0.77; making the recommended invocation:
use version 1.00; $our $VERSION = qw("v1.2.3");
This still confuses me as I think that:
use
15 matches
Mail list logo
