Yeah..I guess if I want the “over all holistic look”, I probably need to
just volunteer to do it!
And honestly, maybe we make too big of a deal of CHANGES.txt?
> On Jul 26, 2024, at 6:58 AM, Gus Heck wrote:
>
> There is currently such a step, but it's focused on looking for duplicate
>
There is currently such a step, but it's focused on looking for duplicate
entries. Editorial review at release time is difficult because Solr is so
big, and probably almost nobody stays on top of all the changes. Review at
PR/Checkin would seem to me to be the best route.
On Wed, Jul 24, 2024 at 2
Fair on the “make work” side of things. I know I skim through it at various
times, but we also have our Migration guide in the Ref Guide too….
I do look forward to a future with a simpler less confusing CHANGES.txt!
> On Jul 24, 2024, at 2:21 PM, David Smiley wrote:
>
> I like the idea yet I
I like the idea yet I also wonder if most folks simply won't care to
provide any input anyway, and then it becomes just yet another release
task. Also, I wouldn't want to recommend any process that would need
to be rethought if we streamline CHANGES.txt management (e.g. we spoke
of using separate
I was thinking that as part of our release process we should have a “review
CHANGES.txt” step? I don’t know if that is already in there, but it might be
a good step for us as a community to have a single point in time to review that
to make sure it’s clear and accurate….
We have lots of fol
