Boost logo

Boost :

Subject: [boost] Trac system Milestone
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2009-02-11 04:57:05


Hi,

I see in the Trac system that there are bugs with Milestone 1.36, 1.37. 1.38 and To be determined.

As we will not have 1.36.x, 1.37.x releases, and possibly neither 1.38, shouldn't we change the Milestone to 1.39?
For the To be determined, shouldn't we change to the corresponding Milestone Boost 1.39, Boost.Jam 3.1.18
Boost.Jam 4.0.0, Website 1.X. Maybe the ToBeDetermined Milestone is not a good idea. I have not counted the tickets without a Milestone, I don't know how to do.

BTW, Should'nt the version be a mandatory field?

As there are 196 + 97 + 156 + 181= 630 tickets to change it would be great if there is an easy way to do that.

Best,
Vicente

Milestone: Boost 1.36.0
Completed 6 months ago (08/15/08)
62%
Closed tickets:
324
Active tickets:
196
/ Total tickets:
520

Milestone: Boost 1.37.0
Completed 3 months ago (11/02/08)
55%
Closed tickets:
120
Active tickets:
97
/ Total tickets:
217

Milestone: Boost 1.38.0
Completed 7 hours ago (02/10/09)
38%
Closed tickets:
96
Active tickets:
156
/ Total tickets:
252

Milestone: To Be Determined
61%
Closed tickets:
279
Active tickets:
181
/ Total tickets:
460


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk