Hi Christian,

I imagined that this would be your response, but I wanted to bring it
forward so that others ( and you ) are aware of it. Out of curiosity,
will you always send timestamps in UTC ( ending in 'Z' ) or will you
use the timezone modifier of the Reviewboard installation, e.g. +01:00
?

Robert

On Wed, Jan 23, 2013 at 12:33 AM, Christian Hammond <chip...@chipx86.com> wrote:
> Hi Robert,
>
> Unfortunately, this is just the reality of the 1.7 release. We moved to a
> newer version of Django that changes how timestamps are stored. From here on
> out, they'll never change again, but they will require clients to be
> flexible in how they handle formatted timestamps if they want to support
> pre-1.7 releases.
>
> The reason the 1.6 docs are showing the newer timestamp is that the payloads
> are computed at doc generation time, and it's using a newer version of
> Django. There's work I need to do to fix this, and it's something I'm hoping
> to get to, but it's lower priority than some things I have to take care of
> right now :/
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
> On Jan 22, 2013, at 1:15 PM, Robert Munteanu <robert.munte...@gmail.com>
> wrote:
>
> Hi,
>
> I am the current maintainer of the Reviewboard integration for Eclipse [1] .
> I was notified by several users that the plugin broke with 1.7, due to date
> formatting differences [2] . Apparently for 1.6 a formatted date is
> '2010-08-28 02:26:18.474' while for 1.7 it is '2010-08-28T02:26:18.474Z'  (
> BTW, there is an incorrect format listed at [3] for 1.6 ; that does not
> match what 1.6 currently does ).
>
> While I agree that ISO 8601 is a good, non-ambiguous way of formatting
> dates, it does break backwards compatibility with existing clients, and
> forces those which need to support both 1.6 and 1.7 to assume ( or accept )
> more than they should. It would be good to have a standard way of formatting
> dates across versions.
>
> Thanks,
>
> Robert
>
> [1]: https://github.com/rombert/ereviewboard
> [2]: http://github.com/rombert/ereviewboard/issues/issue/11
> [3]:
> http://www.reviewboard.org/docs/manual/1.6/webapi/2.0/resources/review-request/
>
> --
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/donate/
> Happy user? Let us know at http://www.reviewboard.org/users/
> -~----------~----~----~----~------~----~------~--~---
> To unsubscribe from this group, send email to
> reviewboard+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/reviewboard?hl=en
>
>
>
>
> --
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/donate/
> Happy user? Let us know at http://www.reviewboard.org/users/
> -~----------~----~----~----~------~----~------~--~---
> To unsubscribe from this group, send email to
> reviewboard+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/reviewboard?hl=en
>
>



--
Sent from my (old) computer

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en


Reply via email to