DateTime wiki is back
The wiki should be back (http://datetime.perl.org). Please let me know if you find any breakage (besides user images, which I know are broken) -dave /* http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) */
Re: 1) Datetime website 2) recommended practice to alter API
On Fri, 27 Sep 2013, Jean Forget wrote: When I try to access the http://datetime.perl.org/wiki/datetime/ website, I get: --- begin of copy-paste Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. --- end of copy-paste Can you check the web server, please? My server crashed hard on Monday. I've moved to Linode but I haven't quite gotten everything running again. Another question is: which is the earliest Perl version should we target? Dave wanted to target 5.005 or maybe 5.004, but that was more or less 10 years ago, when the 5.8 version was reigning supreme. But now, we have reached 5.18 and 5.14 is no longer officially supported. I'd say 5.8 or 5.10. Unfortunately, while p5p may only support 5.16+, there are still distributions in wide use like RHEL that use old Perls. -dave /* http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) */
Re: 1) Datetime website 2) recommended practice to alter API
Jean Forget wrote: >-- how much time should pass between two steps? In situations like this, I'd accept the old keyword forever, never even making it warn. The ability to use the clearer keywords is a desirable feature, but not a good reason to make the original keywords stop working. >-- in step 1, should the module emit a warning if both keywords >are used at the same time? (I think yes) It should be a hard error, generating an exception, not a warning. >Another question is: which is the earliest Perl version >should we target? Depends on the target audience. You shouldn't go to extra effort to support anything earlier than around 5.12 unless you have a specific user who can't upgrade Perl. Targeting earlier than 5.6 is a pain because the "our" keyword isn't available earlier. Personally I routinely test my CPAN modules against almost all versions back to 5.6.1, but I'm unusual in that regard. -zefram
1) Datetime website 2) recommended practice to alter API
When I try to access the http://datetime.perl.org/wiki/datetime/ website, I get: --- begin of copy-paste Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. --- end of copy-paste Can you check the web server, please? -- I wanted to find if the website has any advices on programming or on managing module releases. My present concern is https://rt.cpan.org/Public/Bug/Display.html?id=77710 replacing the API keyword "iteration" with "precise" in DateTime::Event::Sunrise. And I have at least one other keyword change (altitude -> height) The various steps would be: 1) silently accept both old and new keywords 2) accept both keywords, but emit a warning if the old keyword is used 3) accept only the new keyword. My questions are: -- how much time should pass between two steps? -- in step 1, should the module emit a warning if both keywords are used at the same time? (I think yes) Another question is: which is the earliest Perl version should we target? Dave wanted to target 5.005 or maybe 5.004, but that was more or less 10 years ago, when the 5.8 version was reigning supreme. But now, we have reached 5.18 and 5.14 is no longer officially supported. Jean Forget
