There was a recent conversation in priv...@solr.apache.org that should
not have been conducted there so I am moving it to the dev list. I
intend to hold a VOTE to formalize the decision soon. It would be a
procedural vote and as-such needs a majority of voters approving for
it to pass.
--
Sometimes we make changes and forget to run tidy. It's rather annoying.
It occurred to me that our "precommit" GitHub PR action could be modified
to first run tidy and to commit the changes (if any) beforehand, pushing to
the source branch (generally on someone's fork). Here's a blog post with
I found the correct thread, let's discuss there not here.
"Do we require Jira's for bug fixes?" March 2nd
-
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
I can't seem to find the conversation I was thinking of but this one
is close enough.
Can we have more clarity on when a JIRA issue is mandatory? Or the
reverse -- give clarity that small bugs don't need a JIRA issue. My
goal is to remove/reduce barriers for contributors as much as
possible.
The migration of the commands from zkcli.sh over to the bin/solr zk subcommands
structure is ready for review. https://github.com/apache/solr/pull/2298
The plan is to keep zkcli.sh on 9x, and remove it in 10.
I’m also going to migrate the ./server/scripts/cloud-scripts/snapshotcli.sh
over
Sounds good…. BTW, I’d like to make a plug for C/C NA, apparently the CfP is
wrapping soon!
> On Mar 21, 2024, at 10:49 PM, David Smiley wrote:
>
> Sounds good; I can probably join then. Thanks for organizing!
>
> On Thu, Mar 21, 2024 at 11:26 AM Jason Gerlowski
> wrote:
>>
>> Hey all,
