generate_milestones.py carries a hardcoded set of titles:
BUCKET_TITLES = {"immediate", "needed soon", "needed later", "not urgent"}It exists to recognise the legacy priority-bucket milestones — undated milestones used to rank work rather than to commit to a date. They never close, so sorting them among real deadlines would either bury the deadlines or dress the buckets up as ones. The milestones page puts them in their own section below the release schedule instead, under "Priority buckets (not deadlines)".
It is a workaround for a data problem, not a feature: a milestone should mean a deadline, and these do not. Once the buckets are cleaned up, BUCKET_TITLES, is_bucket(), the bucket flag in milestones.json and the second section of the page all go away together.
Not yet. From a live run this morning, 11 of the 18 open milestones across the five repositories are buckets:
| Repository |
Buckets |
NCATSTranslator/Babel |
Immediate, Needed soon, Needed later, Not urgent |
NCATSTranslator/NodeNormalization |
Needed soon, Needed later, Not urgent |
NCATSTranslator/NameResolution |
Needed soon, Needed later, Not urgent |
TranslatorSRI/babel-validation |
Needed soon, Needed later |
So this is blocked on the cleanup, not on the code. The substitute for what the buckets express is Priority: labels, which already exist and are already in use — see #127.
Related: NCATSTranslator/Babel#1048 covers the ~253 open issues parked in closed buckets, which is the same problem one step further along.
Follow-up to #112.
generate_milestones.pycarries a hardcoded set of titles:It exists to recognise the legacy priority-bucket milestones — undated milestones used to rank work rather than to commit to a date. They never close, so sorting them among real deadlines would either bury the deadlines or dress the buckets up as ones. The milestones page puts them in their own section below the release schedule instead, under "Priority buckets (not deadlines)".
It is a workaround for a data problem, not a feature: a milestone should mean a deadline, and these do not. Once the buckets are cleaned up,
BUCKET_TITLES,is_bucket(), thebucketflag inmilestones.jsonand the second section of the page all go away together.Not yet. From a live run this morning, 11 of the 18 open milestones across the five repositories are buckets:
NCATSTranslator/BabelImmediate,Needed soon,Needed later,Not urgentNCATSTranslator/NodeNormalizationNeeded soon,Needed later,Not urgentNCATSTranslator/NameResolutionNeeded soon,Needed later,Not urgentTranslatorSRI/babel-validationNeeded soon,Needed laterSo this is blocked on the cleanup, not on the code. The substitute for what the buckets express is
Priority:labels, which already exist and are already in use — see #127.Related: NCATSTranslator/Babel#1048 covers the ~253 open issues parked in closed buckets, which is the same problem one step further along.
Follow-up to #112.