This has been discussed and documented before: https://cwiki.apache.org/confluence/display/SOLR/Commit+Process+Guidelines#CommitProcessGuidelines-UpdatingCHANGES.txt
In general I push for us to not waste our time on busy-work like this, not to mention hassling everyone else in perpetuity who reads the CHANGES.txt to read that some test doesn't need a dependency it once needed ;-). Fundamentally ask yourself *who cares*? Are there user perceivable consequences? Are there non-trivial risks? ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Wed, Feb 16, 2022 at 2:22 AM Eric Pugh <[email protected]> wrote: > Hi all! Do we have a written definition of what requires a JIRA and/or > an entry in CHANGES.txt? Something that could go in our developer docs? > > Is there a consensus on this? For example, changes to documentation > typically have NOT gone into the CHANGES.txt file. It appears that some > refactoring don’t need a JIRA issue as well. > > Thoughts on this? > > > Eric > > _______________________ > *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467 > | http://www.opensourceconnections.com | My Free/Busy > <http://tinyurl.com/eric-cal> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed > <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> > This e-mail and all contents, including attachments, is considered to be > Company Confidential unless explicitly stated otherwise, regardless > of whether attachments are marked as such. > >
