ssl option must now be passed

[karenetheridge]

...otherwise, this warning is spewed from Net::Twitter:

The Twitter API now requires SSL. Add ( ssl => 1 ) to the options passed to new
to enable it. For backwards compatibility, SSL is disabled by default in this
version. Passing the ssl option to new will disable this warning. If you are
using a Twitter API compatbile service that does not support SSL, add
( ssl => 0 ) to disable this warning and preserve non-SSL connections in future

[karenetheridge]

BTW your use of 3-part versions makes it harder to insert a new version between 2.0.1 and 2.0.2 for local installs... please consider switching to a regular decimal.

http://www.dagolden.com/index.php/369/version-numbers-should-be-boring/

[karenetheridge]

Also BTW - the repo only contains 2.0.1 but PAUSE has 2.0.2. Please update github!

[yanick]

On its way to CPAN. Thanks!

As for the release version. I am very aware of David's article, and I concede that the reasonable thing is probably to go to a one-digit version. But I really, really like the concept of semantic versioning and... well, this is one of the rare instances where I allow myself not to be reasonable. Hopefully, in the grander scheme of things, my karma will balance out.

I must say, though, it's the first time I herd the argument of leaving that sub-version third place open for local installs. That's a neat trick.

[karenetheridge]

On Tue, Jan 21, 2014 at 07:24:55PM -0800, Yanick Champoux wrote:

On its way to CPAN. Thanks!

w00t, thanks!

As for the release version. I am very aware of David's article, and I concede that the reasonable thing is probably to go to a one-digit version. But I really, really like the concept of semantic versioning and... well, this is one of the rare instances where I allow myself not to be reasonable. Hopefully, in the grander scheme of things, my karma will balance out.

You can still use semver without the extra dot... just $VERSION + 0.000001 for
normal releases, and $VERSION + 0.001 for major releases.

I must say, though, it's the first time I herd the argument of leaving that sub-version third place open for local installs. That's a neat trick.

well there's always the fourth dot... which I'd forgotten was legal when I
wrote that comment.

[yanick]

On Tue, Jan 21, 2014 at 07:53:17PM -0800, Karen Etheridge wrote:

w00t, thanks!

No, no, thank /you/. :-)

You can still use semver without the extra dot... just $VERSION + 0.000001 for
normal releases, and $VERSION + 0.001 for major releases.

Yeah, I know... I know... I should probably let go of that little dot. Adding support
for that particular scheme is already in my plans for my SemanticVersion dzil plugin.
I just have to kick myself, grind my teeth and do it.

I must say, though, it's the first time I herd the argument of leaving that sub-version third place open for local installs. That's a neat trick.

well there's always the fourth dot... which I'd forgotten was legal when I
wrote that comment.

It is? That's a surprise. I was sure that the fun stopped at 3 parts. But no, you are
right, it's sub-sub-versions all the way down!

... oh boy. No good can come out of that new knowledge, can it? ;-)