Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/767
@ottobackwards , regarding the version references in
metron-analytics/metron-profiler/README.md:
This is a little difficult. Although these are installation instructions,
the lines you grepped are all OUTPUT from `find` or `rpm`. In use with an
0.4.2 code base, the actual output will be the correct-in-that-context 0.4.2
filenames and pathnames. So while user might be surprised at first, they will
not (if they're following instructions) be caused to type incorrect commands.
And since 0.4.2 hasn't been released yet, there is no date field that I can
substitute for `201707131420` would be "correct" with 0.4.2.
I think it's best to leave it the way it is. If you prefer a different
rendering, please propose.
Regarding the line from metron-analytics/metron-profiler-client/README.md
that has an 0.4.1, this is in the text of an example, and does not materially
affect the example. Therefore, as noted in the opening comments of this PR, it
is my policy to leave it unchanged. "If you grep for `0.4.1` (or rather for
`0\\.4\\.1`), you'll find some remaining usage of 0.4.1 in documentation files,
where I judged the usefulness of an example did not require updating the
version number."
Open to discussion, of course. But by following this policy, those (many)
lines of text fall out of the grep on the next generation (when moving from
0.4.2 to 0.4.3). Which makes release management much easier.
---
