A project is a way of organizing work by keeping track of who is working
on what and at what stage a particular part of the project is. A
milestone tracks absolute progress toward some goal, which is all I'm
seeking to accomplish.
I wouldn't be opposed to creating a project as well, but I'm skeptical
that it would be used.
On 8/5/19 3:02 PM, Jeremy Mitchell wrote:
I've just always associated milestone with release for some reason...
Feels like a "project" to me however. Oh look at that there was one for
this at one time:
https://github.com/apache/trafficcontrol/projects?query=is%3Aclosed
On Mon, Aug 5, 2019 at 2:56 PM ocket8888 <[email protected]> wrote:
As far as I know, the only thing you get with a Milestone (immediately
and by default) that doesn't come with a label is the ability to track
progress towards reaching that milestone. Which I think is appropriate
here - and is actually all of my motivation for suggesting a milestone
rather than a label. What "baggage" do you mean?
On 8/5/19 2:52 PM, Chris Lemmons wrote:
I agree that separate tickets is ideal. Would a tag work for this
purpose? Milestones have other baggage that doesn't apply here.
On Mon, Aug 5, 2019 at 2:16 PM ocket 8888 <[email protected]> wrote:
Currently to see what endpoints are rewritten and which still need to be
done, you need to check out this one, specific issue Rob made forever
ago:
https://github.com/apache/trafficcontrol/issues/2232
I think it'd be better to give each endpoint its own Issue - only the
ones
that still need to be rewritten - and then link them all in a "Go
Rewrite"
milestone. It's much easier to organize. Then we can stop re-building
this
list.
I volunteer to comb through the list and figure out what endpoints
actually
are rewritten and do the work of creating issues for them, provided
that's
acceptable to everyone? I think we typically only use milestones for
releases, so I thought I should check.
