Age field in revisions is too coarse

[jtiai <redetin@…>]

As date 2007-12-07 (ISO format date) I've two files commited in my repository. Both states age as "2 years" but closer inspection revealed that another was changed at 2005-07-13 and another 2006-05-30.

Error margin (almost 25%) is a bit too high considered that project itself is about 2 and half years old.

[sid]

Just to clarify your request, are you asking for "Modified 2.5 years ago" or a decimal point for more information?

I like that dates/times are rounded to whole numbers. Quick and easy to visually scan. Approx age at that point is good enough for stuff we do.

[Christian Boos]

I think he was requesting that we use the previous unit for a range of values a bit extended, e.g.

trac/util/datefmt.py

@@ -85 +85 @@
         return '%i second%s' % (age_s, age_s != 1 and 's' or '')
     for u, unit, unit_plural in units:
         r = float(age_s) / float(u)
-        if r >= 0.9:
+        if r >= 1.9:
             r = int(round(r))
             return '%d %s' % (r, r == 1 and unit or unit_plural)
     return ''

This shows things like 23 months.

Note that the patch doesn't work for seconds though, at least it uncovered a bug in get_timeline_link.

I'm siding with sid against decimal output if that's what was actually requested, but I think showing 2 years only if the age is actually above 23 months is better.

[Christian Boos]

Above patch applied in r6658.