Release time is fine in my opinion. If they are automated, I wasn't
recalling it. People running unreleased code can reasonably be expected to
do their own homework, and watch commits etc. However people deciding if
they will conduct an upgrade to a new release, or how to prepare for it
will want t
>From what I understood, entries in CHANGES.txt are automatically added
during release processes, so no actions are necessary from the developer's
point of view when merging the Solrbot PRs.
If I get you right Gus, you'd like to see at least these entries earlier,
and the changes should contain th
So after a bit of trying around, I am facing the error message on Mac and
Windows with the latest stable IDE version of IntelliJ. The error message is
returned at the end of every ./gradlew check and is probably coming from the
IDE and not Gradle itself. Just for reference what the message looks
That's far more polite than the linux edition, where it is much less
helpful and entirely fails to run:
Invalid Gradle JDK configuration found. Open Gradle Settings
On Sat, Oct 26, 2024 at 10:30 AM Christos Malliaridis <
malliari...@apache.org> wrote:
> So after a bit of trying around, I am faci
Changes in our dependencies ought to be tracked somewhere more digestible
than VCS. Users who use our test framework or have repositories containing
custom code intended to run inside of solr will care about changes in deps
for both solrj, and core, and whatever components. CHANGES.txt isn't great
I assume waiting any longer will not make much sense, so I am going forward and
start merging at least the "easy" dependency updates. I will also look into
documenting any experience / process at the end, so that others will have it
easier to address dependency updates in the future.
Keep an ey
