[tahoe-dev] Milestone options for trac

David-Sarah Hopwood david-sarah at jacaranda.org
Wed Jan 27 03:37:37 UTC 2010

Terrell Russell wrote:
> On 1/26/10 9:22 PM, David-Sarah Hopwood wrote:
>>> Changes (by zooko):
>>>   * milestone:  1.6.0 => eventually
>> It would be good if we could add some more precise milestone options.
>> There are 133 tickets with milestone "eventually"!
>> I suggest adding at least "1.7.0" and "soon".
> And curious to me - what is the true nature of these tickets?
> marked eventually, but also marked closed.
> http://allmydata.org/trac/tahoe/query?status=closed&group=resolution&milestone=eventually

That's an interesting question. Here they are grouped by Resolution:


For the ones that are closed as wontfix, invalid, or duplicate, the
Milestone field at the time they were closed is irrelevant and can be

For the ones that were closed as fixed, in some cases the Milestone should
have been updated to indicate the version in which they were fixed.
In some cases that's not necessary because the fix is not associated with
a particular version of Tahoe. For example, the first ticket listed, #45,
is a fix in Trac (so actually should have been marked invalid as a Tahoe
bug, if we're being picky). Some just got forgotten and closed only a long
time after the fix -- for example #183 which was fixed "forever ago" :-)

OTOH, earlier versions aren't listed as Milestone options, so if any
tickets should have an earlier version in that field, it can't be corrected
at the moment. There are only 34 of these tickets, so it's not a big issue.

David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 292 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100127/e52f5399/attachment.asc>

More information about the tahoe-dev mailing list