Merge lp:~ltrager/maas/lp1598461 into lp:~maas-committers/maas/trunk
Proposed by
Lee Trager
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Lee Trager | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 5161 | ||||
Proposed branch: | lp:~ltrager/maas/lp1598461 | ||||
Merge into: | lp:~maas-committers/maas/trunk | ||||
Diff against target: |
75 lines (+36/-4) 2 files modified
src/maas/settings.py (+3/-3) src/maasserver/views/tests/test_images.py (+33/-1) |
||||
To merge this branch: | bzr merge lp:~ltrager/maas/lp1598461 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gavin Panella (community) | Approve | ||
Review via email: mp+299371@code.launchpad.net |
Commit message
Show image last update using the time format consistent with other areas of the MAAS UI
Description of the change
The images page is generated with a Django template. While we convert the last update field for Ubuntu images we let Django handle the conversion of a datetime object for other image types. Because we set USE_L10N = True in maas/settings.py Django converts the datetime object using its default format which differs from the format we use in the rest of MAAS.
To post a comment you must log in.
> While we convert the last update field for Ubuntu images we let Django
> handle the conversion of a datetime object for other image types.
That makes it sound like the fix in this branch is cosmetic only, in
that it makes everything look the same but isn't consistent.
It would be best if date fields for all images are treated consistently,
so that a future maintainer doesn't have to figure out which way to do
it.
> Because we set USE_L10N = True in maas/settings.py Django converts the
> datetime object using its default format which differs from the format
> we use in the rest of MAAS.
Perhaps we should switch this to False instead of overriding its effects
at the edges of the application? Any guesses as to what the fallout
would be?