Can someone expand on the downsides of having the Kotlin UI code in
the main repo? Or the concrete benefits of separating it out?
I know there were some CI job failures around the time of the initial
merge, but I haven't noticed it causing issues after that - did I miss
some other discussion wher
Yeah, I am a bit suss of having it be in it's own repo. If it's in it's own
repo, folks won't know about it, and it'll struggle to gain traction. We've
gone down the separate repo path with some other efforts, like the Yet Another
Solr Admin UI project.
Having it not build on various arc
Jason, if you look at the policeman jenkins, you will see a lot of
failures. (Because of alternate JDK support). You will also see failures
for https://ci-builds.apache.org/job/Solr/job/Solr-Test-main-s390x/ because
that architecture isn't supported. There are a few other jenkins failures,
but the
Please vote for release candidate 1 for the Solr Operator v0.9.1
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/solr/solr-operator/solr-operator-v0.9.1-RC1-rev099a38bf7716fa645a8fae6ad34b7922ccd5d4ff
You can run the full smoke tester, with instructions below.
However
I've uploaded some "Draft" release notes for 0.9.1; please take a look
and review if you have a few minutes!
https://cwiki.apache.org/confluence/display/SOLR/Solr+Operator+Release+Notes+v0.9.1
Best,
Jason
On Mon, Mar 17, 2025 at 1:32 PM Jason Gerlowski wrote:
>
> Excellent, looks like all of t
I was considering this from the beginning, and I was not aware of the whole
stack we were using for building Solr. I thought that the GitHub workflows
would be sufficient to guarantee at least the build processes to succeed in
all our CI/CD environments, but I was wrong.
Since the UI is generating
Excellent, looks like all of the blockers mentioned last week are
cleared up; will start on the first RC now!
Best,
Jason
On Thu, Mar 13, 2025 at 1:23 PM Houston Putman wrote:
>
> I'm adding https://github.com/apache/solr-operator/issues/761 as a blocker,
> but there is an easy fix! https://git
