64bit duration almost working - mongo problem still there
Merge remote-tracking branch 'origin/feature/ipv6_support' into bug/int64_for_duration_and_throttling
Merge remote-tracking branch 'origin/feature/ipv6_support' into bug/int64_for_duration_and_throttling
Merge branch 'develop' into bug/int64_for_duration_and_throttling
64 bits expiration in mongo
Merge branch 'develop' into bug/int64_for_duration_and_throttling
Fixed a indentation error and some more 'L's for long
CHANGES_NEXT_RELEASE
CHANGES_NEXT_RELEASE
FIX references to issues at GitHub in CHANGE_NEXT_RELEASE past entries
more 64bit stuff for subscriptions
Merge remote-tracking branch 'origin/bug/int64_for_duration_and_throttling' into bug/int64_for_duration_and_throttling
Now parse8601 detects that 'PY99' is syntactically incorrect
extracting long long from mongo for expiration
Removed a FIXME that is fixed in this PR
LONG expiration harness test
moved bad duration poart to separate harness test
Merge pull request #230 from telefonicaid/bug/int64_for_duration_and_throttling

Bug/int64 for duration and throttling