And yes, if it's not clear, I've lost 80-90% of these same work before.
Total idiot.
- Mark
On Mon, Oct 21, 2019 at 8:56 PM Mark Miller wrote:
> The branch is there, certainly it can go in without me.
>
> It does need the settings.xml fix. When I think about timing, my main
> concern is my
The branch is there, certainly it can go in without me.
It does need the settings.xml fix. When I think about timing, my main
concern is my availability - I'll be gone nov 14 to the end of the month
and then holidays are busy. If others want to take on the responsibility
though, I would not stop
Sure, Cassandra. Sounds good.
On Tue, Oct 22, 2019 at 1:00 AM Cassandra Targett wrote:
>
> On Oct 19, 2019, 1:32 PM -0500, Ishan Chattopadhyaya
> , wrote:
>
> Thanks a lot Andrzej and Shalin.
> I'll try to build the RC on Monday. FYI, upon Jan's advice, I'll be using his
> release wizard tool.
+1 to re-spin if this can be fixed quickly enough.
On Tue, Oct 22, 2019 at 3:30 AM David Smiley wrote:
>
> I just discovered this: https://issues.apache.org/jira/browse/SOLR-13855
> which is in effect since 8.1, Distributed URP in cloud mode doesn't propagate
> finish(). I see that Run URP
I just discovered this: https://issues.apache.org/jira/browse/SOLR-13855
which is in effect since 8.1, Distributed URP in cloud mode doesn't
propagate finish(). I see that Run URP further propagates this to the
UpdateLog. Not doing this looks concerning to me. The bug should be easy
to fix,
Hi,
Policeman Jenkins also verified the release for me:
SUCCESS! [2:49:07.411227]
Finished: SUCCESS
https://jenkins.thetaphi.de/job/Lucene-Solr-Release-Tester/26/console
I also downloaded it and did some checks in documentation and so on. I had not
enough time to start up solr, I only looked
Since we’re only sort of half-way through revamping the Solr Ref Guide release
process, I’ve manually pushed up the 8.3 Ref Guide with a DRAFT watermark if
anyone would like to review it while looking at the packages:
https://lucene.apache.org/solr/guide/8_3/.
Cassandra
On Oct 21, 2019, 2:17
On Oct 19, 2019, 1:32 PM -0500, Ishan Chattopadhyaya
, wrote:
> Thanks a lot Andrzej and Shalin.
> I'll try to build the RC on Monday. FYI, upon Jan's advice, I'll be using his
> release wizard tool. Also, I'll need to dig into the simultaneous refguide
> release situation. So, i might need
Super minor documentation note:
In the HTML changes file, the parsing of - I guess - SOLR-12368 record
makes the authors information become a separate point.
Please vote for release candidate 1 for Lucene/Solr 8.3.0
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.3.0-RC1-revd796eca84dbabe3ae9b3c27afc01ef3bee35acb1
You can run the smoke tester directly with this command:
python3 -u
Going out on a limb here, as in “this may be a whacky idea but let’s toss it
around anyway”.
- Check in the test fixes and Gradle build in the current state to master/9.0
as soon as possible. Essentially let it break however it will, even if that
means we shut off Jenkins for a while. Or only
agree with david
as your schedule gets packed there are more than a few that are willing to
pickup the slack
if the branch is checked-in and labelled we can tackle what needs to be done
From: David Smiley
Sent: Monday, October 21, 2019 2:13 AM
To: Mark Miller
Thanks for clarifying, Mark. We all have real jobs (and life) so
delays are I think understandable. I tend to agree with David that
even something that is slow at start has benefits but I respect your
will to keep the partial work unpublished.
I've made some changes here and there (the original
Thanks for your efforts Mark!
Why has the migration to Gradle somehow been blocked by performance
improvements to Solr's tests?
What are the blockers to the Gradle branch being merged to master? It's an
experimental shadow build, so... none?
I appreciate you want everything to be great from the
14 matches
Mail list logo
