Re: Best way to communicate changing the output of a module

On 13-12-26 11:16 AM, David Mertens wrote: This would be dependency hell. I think a prominent warning (as suggested by Aristotle) would be much better. Probably a better first approach, all in all. Assuming that this is not just over-engineering, considering how semantic versioning is still a

Re: Best way to communicate changing the output of a module

`/anick - This would be dependency hell. I think a prominent warning (as suggested by Aristotle) would be much better. Whether we should have this sort of environment variable around is a good question. How would we develop an awareness and use of this variable? David On Sun, Dec 22, 2013 at 11

Re: Best way to communicate changing the output of a module

To expand on Leon's suggestion, you could also provide some simple constants for often-used date/time formats, making it even easier for your users to invoke standard formatting. David On Mon, Dec 23, 2013 at 9:45 AM, Leon Timmermans wrote: > On Mon, Dec 23, 2013 at 12:48 PM, Shmuel Fomberg >

Re: Best way to communicate changing the output of a module

On Mon, Dec 23, 2013 at 12:48 PM, Shmuel Fomberg wrote: > Hi Stephen. > > On Fri, Dec 20, 2013 at 2:32 AM, Stephen Patterson wrote: > > >> I'm the maintainer of Finance::Bank::CooperativeUKPersonal, a module for >> downloading UK bank statements. Part of the output from this module is a >> stateme

Re: Best way to communicate changing the output of a module

Hi- One option that could be used for immature module distributions is to release them as CPAN developers releases, e.g. with a '_01' in the distribution name. That will allow users to install from CPAN via an explicit distribution request but it will not be official until the first non-developer

Re: Best way to communicate changing the output of a module

Hi Stephen. On Fri, Dec 20, 2013 at 2:32 AM, Stephen Patterson wrote: > > I'm the maintainer of Finance::Bank::CooperativeUKPersonal, a module for > downloading UK bank statements. Part of the output from this module is a > statement date in dd/mm/ (UK) format. As I've started using the modul

Re: Best way to communicate changing the output of a module

* Yanick Champoux [2013-12-22 20:35]: > Perhaps a saner middle-ground could be of introducing a new > environment variable CPAN_NO_MAJOR_JUMP. Or just warn instead of dying. -- Aristotle Pagaltzis //

Re: Best way to communicate changing the output of a module

On 13-12-20 01:25 PM, Karen Etheridge wrote: I don't think it's wise to assume any connection between a module's version and its stability, unless the documentation explicitly says so. This touches a side-thought that has been on my mind for a little while, and I'm curious to see what other au

Re: Best way to communicate changing the output of a module

On Fri, Dec 20, 2013 at 02:59:41PM +, Matthew Astley wrote: > As you're well under the magic 1.00 version number, you could probably > just change it and mention this in the release notes. Giving useful > error messages will ease the transition. > > I tend to imagine that anyone pointint a 0.

use Module VERSION ... Re: Best way to communicate changing the output of a module

On Fri, Dec 20, 2013 at 10:38:38AM -0500, Yanick Champoux wrote: > [... you could ] adopt the new behavior if the module is called with > the new version 'use Finance::Bank::CUKP 1.23;'. If the module is > called with no version or an older version, you keep the old > behavior, but issue a depreca

Re: Best way to communicate changing the output of a module

On Thu, Dec 19, 2013 at 05:32:57PM +, Stephen Patterson wrote: > I'm the maintainer of Finance::Bank::CooperativeUKPersonal, a module > for downloading UK bank statements. Part of the output from this > module is a statement date in dd/mm/ (UK) format. As I've > started using the module, I'

Re: Best way to communicate changing the output of a module

On Thu, Dec 19, 2013 at 05:32:57PM +, Stephen Patterson wrote: > [...] I'm considering changing this to ISO-SQL standard - > -mm-dd. What's the best way of communicating this change & > managing things during changeover? As you're well under the magic 1.00 version number, you could probab

Best way to communicate changing the output of a module

Hi All I'm the maintainer of Finance::Bank::CooperativeUKPersonal, a module for downloading UK bank statements. Part of the output from this module is a statement date in dd/mm/ (UK) format. As I've started using the module, I'm considering changing this to ISO-SQL standard - -mm-dd.