off by one in membership expiry date handling

Bug #619522 reported by James Troup
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

If I add someone to a group and set them to expire on 2010-08-19, they're displayed as expiring on 2010-08-18. If I go back in and change that to 2010-08-20, they're displayed as expiring on 2010-08-19.

Revision history for this message
Curtis Hovey (sinzui) wrote :

This is very odd. I wonder if this will "fix" itself when DST ends. This needs looking into.

affects: launchpad → launchpad-registry
Changed in launchpad-registry:
importance: Undecided → Low
status: New → Triaged
Curtis Hovey (sinzui)
tags: added: teams
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.