My 2 cents: all this cloud provider etc stuff (backup repositories etc) should be migrated away into a separate repository so that those who consider all this as noise can easily block it out.
On Tue, 9 Apr, 2024, 5:32 pm Eric Pugh, <ep...@opensourceconnections.com> wrote: > The update that I see a lot is for the software.amazon.awssdk and > com.google.cloud packages…. I checked renovate.json and they should only > happen once a month. > > I just checked and there has been an update today, yesterday, and the day > before for the software.amazon.awssdk package. > > Looks like they all go to https://github.com/apache/solr/pull/2056 > however. Is this because once it opens the PR, it is just updating the PR > as needed? > > How can we get a smoother workflow? The constant updates are noisy, and > now I think they are just ignored…! I saw that Kevin approved this back > in November 2023. Do we want to be more on top of these and merge as they > go? > > And maybe for these frequently changing ones, maybe move to a quarterly > schedule? Or, do we add it to the release manager process, though I know > that approach was discussed and then viewed as too burdensome for the RM. > > > > Eric > > > > > > _______________________ > Eric Pugh | Founder | OpenSource Connections, LLC | 434.466.1467 | > http://www.opensourceconnections.com < > 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. > >
