Github user sudheerv commented on the pull request:
https://github.com/apache/trafficserver/pull/554#issuecomment-214693606
The problem is that you are trying to "mix" the internals of a completely
independent/different feature to use for an unrelated/unintended purposes. This
sets a bad precedent and makes the code harder to maintain.
You are looking at one specific example where it seems to be conveniently
doing what you need "right now" - but, just bcoz it seems to be satisfying the
needs right now doesn't mean it will continue to do so in the future, since
milestones is a different feature/function intended to do completely different
things. If tomorrow someone changes milestone implementation which is not
entirely unlikely, it affects the rest of the code that depends on it so
tightly because of its usage as "more" than milestones. Again, you might argue
that when changing milestones one could also go ahead and change the rest of
the code that "depends" on it. But, you now probably see the issue there? Think
of people following the precedent set and start to randomly use milestones all
over the place for various unrelated purposes. Milestones feature is no longer
doing just milestones :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
