- New upstream release 1.42
- The DateTime::Duration->add and ->subtract methods now accept
DateTime::Duration objects; this used to work by accident but is now done
intentionallay, with docs and tests (GH#50)
- New upstream release 1.41
- The DateTime->add and ->subtract methods now accept DateTime::Duration
objects; this used to work by accident but is now done intentionally, with
docs and tests (GH#45)
- New upstream release 1.39
- Replaced Params::Validate with Params::ValidationCompiler and Specio
- In my benchmarks this makes constructing a new DateTime object about 14%%
faster
- However, it slows down module load time by about 100 milliseconds (1/10
of a second) on my desktop system with a primed cache (so really
measuring compile time, not disk load time)
- When you pass a locale to $dt->set you will now get a warning suggesting
you should use $dt->set_locale instead (CPAN RT#115420)
- Bump minimum required Perl to 5.8.4 from 5.8.1
- Use NO_PERLLOCAL=1 so we can use "make install"
- New upstream release 1.35
- Use namespace::autoclean in all packages that import anything; without
cleaning the namespace, DateTime ends up with "methods" like try and catch
(from Try::Tiny), which can lead to very confusing bugs (CPAN RT#115983)
- New upstream release 1.33
- When you pass a locale to $dt->set you will now get a warning suggesting
you should use $dt->set_locale instead (CPAN RT#115420)
- Added support for $dt->truncate( to => 'quarter' ) (GH#17)
- Fixed the $dt->set docs to say that you cannot pass a locale (even though
you can but you'll get a warning) and added more docs for $dt->set_locale
- Require DateTime::Locale 1.05
- Require DateTime::TimeZone 2.00
- Take advantage of NO_PACKLIST option in recent EU:MM
- New upstream release 1.28
- Fixed handling of some floating point epochs; since DateTime treated the
epoch like a string instead of a number, certain epochs with a non-integer
value ended up treated like integers (Perl is weird) (GH#15, fixes GH#6)
- New upstream release 1.27
- Added an environment variable PERL_DATETIME_DEFAULT_TZ to globally set the
default time zone (GH#14); using this is very dangerous - be careful!
- BR: perl-generators
- New upstream release 1.25
- DateTime->from_object would die if given a DateTime::Infinite object; now
it returns another DateTime::Infinite object (CPAN RT#112712)
- Simplify find command using -empty and -delete
- New upstream release 1.24
- The last release partially broke $dt->time; if you passed a value to use
as unit separator, it was ignored (CPAN RT#112585)
- New upstream release 1.23
- Fixed several issues with the handling of non-integer values passed to
from_epoch() (GH#11)
- This method was simply broken for negative values, which would end up
being incremented by a full second, so for example -0.5 became 0.5
- The method did not accept all valid float values; specifically, it did
not accept values in scientific notation
- Finally, this method now rounds all non-integer values to the nearest
millisecond, which matches the precision we can expect from Perl itself
(53 bits) in most cases
- Make all DateTime::Infinite objects return the system's representation of
positive or negative infinity for any method that returns a number or
string representation (year(), month(), ymd(), iso8601(), etc.); previously
some of these methods could return "Nan", "-Inf--Inf--Inf", and other
confusing outputs (CPAN RT#110341)
- Update DateTime to 0.63
- Update DateTime::TimeZone to 1.22
- DateTime license changed from "GPL+ or Artistic" to "Artistic 2.0"
- Fix DTLocale/Changelog encoding
- use Build.PL as Makefile.PL no longer exists
- use iconv to recode to utf-8, not a patch
- update BuildRequires
- drop Provides: perl(DateTime::TimeZoneCatalog), it is no longer there
- use filtering macros
seems to have been renamed LICENSE.cldr. Update to DateTime::TimeZone
0.54. Use fixperms macro instead of our own chmod incantation. Convert
DateTime::LeapSecond to UTF-8 to avoid a rpmlint warning.
