it's for new and existing requests. Updating the user timezone to
Pacific/Auckland fixed it thanks.
On Monday, January 7, 2013 10:37:03 PM UTC+13, Christian Hammond wrote:
> Hi Christian,
> Is this for new review requests?
> 1.7 added timezone support. If you go into your user settings (My Account
> under your username dropdown on the top bar), you can configure your
> timezone. You should see all times update relative to that timezone.
> The server's timezone settings should ideally be changed to UTC as well.
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
> On Sun, Jan 6, 2013 at 7:12 PM, Christian Wuerdig
> > wrote:
>> Some additional info:
>> The time zone under "General" in Reviewboard is set to Pacific/Auckland
>> If I modify a review request now I get this: Last Updated Jan. 7, 2013,
>> 3:08 a.m.
>> On Monday, January 7, 2013 3:51:21 PM UTC+13, Christian Wuerdig wrote:
>>> after the upgrade to 1.7.1 we can see strange timestamps in the
>>> Like: Posted January 7th, 2013, 2 p.m.
>>> Last Updated: 11 hours, 19 minutes from now
>>> In the REST API for that request:
>>> Local time on the server is Mon Jan 7 15:49:37 NZDT 2013
>>> Seems like there were some changes done on how RB (or Python, or
>>> Django?) deal with different time zones (we are in New Zealand here so
>>> currently we have *UTC/GMT +13 hours)*. It was all working as expected
>>> under 1.6.13.
>>> Anything I missed when upgrading? Any environment variables which need
>>> to be set?
>> Want to help the Review Board project? Donate today at
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> To unsubscribe from this group, send email to
>> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at