You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Alan Woodward <al...@romseysoftware.co.uk> on 2018/02/23 09:50:28 UTC
Lucene/Solr 7.3
Hi all,
It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
- Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 7.3
Posted by Adrien Grand <jp...@gmail.com>.
+1
Le ven. 23 févr. 2018 à 15:32, Ishan Chattopadhyaya <
ichattopadhyaya@gmail.com> a écrit :
> +1.. That gives us enough time to get WIP stuff in.
>
> On Fri, Feb 23, 2018 at 3:20 PM, Alan Woodward <
> alan.woodward@romseysoftware.co.uk> wrote:
>
>> Hi all,
>>
>> It’s been a couple of months since the 7.2 release, and we’ve accumulated
>> some nice new features since then. I’d like to volunteer to be RM for a
>> 7.3 release.
>>
>> I’m travelling for the next couple of weeks, so I would plan to create
>> the release branch two weeks today, on the 9th March (unless anybody else
>> wants to do it sooner, of course :)
>>
>> - Alan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Lucene/Solr 7.3
Posted by Ishan Chattopadhyaya <ic...@gmail.com>.
+1.. That gives us enough time to get WIP stuff in.
On Fri, Feb 23, 2018 at 3:20 PM, Alan Woodward <
alan.woodward@romseysoftware.co.uk> wrote:
> Hi all,
>
> It’s been a couple of months since the 7.2 release, and we’ve accumulated
> some nice new features since then. I’d like to volunteer to be RM for a
> 7.3 release.
>
> I’m travelling for the next couple of weeks, so I would plan to create the
> release branch two weeks today, on the 9th March (unless anybody else wants
> to do it sooner, of course :)
>
> - Alan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Lucene/Solr 7.3
Posted by Erick Erickson <er...@gmail.com>.
+1 Thanks!
On Fri, Feb 23, 2018 at 8:36 AM, Joel Bernstein <jo...@gmail.com> wrote:
> +1
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Fri, Feb 23, 2018 at 10:34 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
>>
>> +1 Thanks!
>>
>> -----
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> http://www.thetaphi.de
>> eMail: uwe@thetaphi.de
>>
>> > -----Original Message-----
>> > From: Alan Woodward [mailto:alan.woodward@romseysoftware.co.uk]
>> > Sent: Friday, February 23, 2018 10:50 AM
>> > To: dev@lucene.apache.org
>> > Subject: Lucene/Solr 7.3
>> >
>> > Hi all,
>> >
>> > It’s been a couple of months since the 7.2 release, and we’ve
>> > accumulated
>> > some nice new features since then. I’d like to volunteer to be RM for a
>> > 7.3
>> > release.
>> >
>> > I’m travelling for the next couple of weeks, so I would plan to create
>> > the
>> > release branch two weeks today, on the 9th March (unless anybody else
>> > wants to do it sooner, of course :)
>> >
>> > - Alan
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 7.3
Posted by Joel Bernstein <jo...@gmail.com>.
+1
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Feb 23, 2018 at 10:34 AM, Uwe Schindler <uw...@thetaphi.de> wrote:
> +1 Thanks!
>
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
> > -----Original Message-----
> > From: Alan Woodward [mailto:alan.woodward@romseysoftware.co.uk]
> > Sent: Friday, February 23, 2018 10:50 AM
> > To: dev@lucene.apache.org
> > Subject: Lucene/Solr 7.3
> >
> > Hi all,
> >
> > It’s been a couple of months since the 7.2 release, and we’ve accumulated
> > some nice new features since then. I’d like to volunteer to be RM for a
> 7.3
> > release.
> >
> > I’m travelling for the next couple of weeks, so I would plan to create
> the
> > release branch two weeks today, on the 9th March (unless anybody else
> > wants to do it sooner, of course :)
> >
> > - Alan
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
RE: Lucene/Solr 7.3
Posted by Uwe Schindler <uw...@thetaphi.de>.
+1 Thanks!
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Alan Woodward [mailto:alan.woodward@romseysoftware.co.uk]
> Sent: Friday, February 23, 2018 10:50 AM
> To: dev@lucene.apache.org
> Subject: Lucene/Solr 7.3
>
> Hi all,
>
> It’s been a couple of months since the 7.2 release, and we’ve accumulated
> some nice new features since then. I’d like to volunteer to be RM for a 7.3
> release.
>
> I’m travelling for the next couple of weeks, so I would plan to create the
> release branch two weeks today, on the 9th March (unless anybody else
> wants to do it sooner, of course :)
>
> - Alan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
Confirmed that this works with Java 10 on MacOS. I’ll start a new build now.
Thanks Uwe!
> On 28 Mar 2018, at 08:23, Uwe Schindler <uw...@thetaphi.de> wrote:
>
> Thanks! What operating system was it?
>
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de <http://www.thetaphi.de/>
> eMail: uwe@thetaphi.de <ma...@thetaphi.de>
>
> From: Varun Thacker <va...@vthacker.in>
> Sent: Wednesday, March 28, 2018 3:31 AM
> To: dev@lucene.apache.org
> Subject: Re: Lucene/Solr 7.3
>
> Tried running Solr's techproducts example from the 7.3 branch with java 8,9,10 and was able to run it successfully
>
> On Tue, Mar 27, 2018 at 1:56 PM, Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de>> wrote:
>> Hi,
>>
>> It’s pushed to 7.3. It would be good if you and some other committers could spend some time to maybe quickly check to start up solr’s techexample with Java 8, Java 9 and also Java 10 on your favourite operating system.
>>
>> Uwe
>>
>> -----
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen <https://maps.google.com/?q=Achterdiek+19,+D-28357+Bremen&entry=gmail&source=g>
>> http://www.thetaphi.de <http://www.thetaphi.de/>
>> eMail: uwe@thetaphi.de <ma...@thetaphi.de>
>>
>> From: Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>>
>> Sent: Tuesday, March 27, 2018 10:31 PM
>> To: dev@lucene.apache.org <ma...@lucene.apache.org>
>> Subject: Re: Lucene/Solr 7.3
>>
>> > I think that's what's happening?
>>
>> Correct - just waiting for SOLR-12141 and I’ll starting building the next RC.
>>
>>
>>> On 27 Mar 2018, at 20:48, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> I have the 7.3 Ref Guide built locally and the PDF has been pushed to the solr-ref-guide-rc SVN repo, but I'm holding off on starting the vote thread until RC2 of 7.3 is available (I think that's what's happening? please correct me if I've misread the threads) so one vote doesn't finish too far ahead of the other.
>>>
>>> Cassandra
>>>
>>> On Mon, Mar 26, 2018 at 9:29 AM, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>> The release candidate is out, everybody please vote!
>>>>
>>>> I’ve drafted some release notes, available here:
>>>> https://wiki.apache.org/solr/ReleaseNote73 <https://wiki.apache.org/solr/ReleaseNote73>
>>>> https://wiki.apache.org/lucene-java/ReleaseNote73 <https://wiki.apache.org/lucene-java/ReleaseNote73>
>>>>
>>>> They’re fairly bare-bones at the moment, if anybody would like to expand on them please feel free.
>>>>
>>>>
>>>>
>>>>> On 21 Mar 2018, at 15:53, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> FYI I’ve started building a release candidate.
>>>>>
>>>>> I’ve updated the build script on 7.3 to allow building with ant 1.10, if this doesn’t produce any problems then I’ll forward-port to 7x and master.
>>>>>
>>>>>
>>>>>> On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi Alan,
>>>>>>
>>>>>> I committed the fix as well as resolve the issue.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> OK, thanks. Let me know when it’s in.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> Hi Alan, guys,
>>>>>>>>
>>>>>>>> I found a blocker issue SOLR-12129, I've already uploaded a patch and beasting the tests, if the result is good I will commit and notify your guys!
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>> Go ahead!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.com <ma...@lucidworks.com>> wrote:
>>>>>>>>>>
>>>>>>>>>> Alan,
>>>>>>>>>>
>>>>>>>>>> I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
>>>>>>>>>>
>>>>>>>>>>> On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
>>>>>>>>>>>
>>>>>>>>>>> +1 to backport your fixes
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>>>>>>>>>>>>
>>>>>>>>>>>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>> Hi guys, Alan
>>>>>>>>>>>>>
>>>>>>>>>>>>> I committed the fix for SOLR-12110 to branch_7_3
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>> Hi Alan,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sure the issue is marked as Blocker for 7.3.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi guys, Alan,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks, Alan
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>>>>>>>>>>>>>>>>> No new features may be committed to the branch.
>>>>>>>>>>>>>>>>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>>>>>>>>>>>>>>>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>>>>>>>>>>>>>>>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>>>>>>>>>>>>>>>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>>>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Mike McCandless
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> - Alan
>>>>>>>>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
RE: Lucene/Solr 7.3
Posted by Uwe Schindler <uw...@thetaphi.de>.
Thanks! What operating system was it?
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de
From: Varun Thacker <va...@vthacker.in>
Sent: Wednesday, March 28, 2018 3:31 AM
To: dev@lucene.apache.org
Subject: Re: Lucene/Solr 7.3
Tried running Solr's techproducts example from the 7.3 branch with java 8,9,10 and was able to run it successfully
On Tue, Mar 27, 2018 at 1:56 PM, Uwe Schindler <uwe@thetaphi.de <ma...@thetaphi.de> > wrote:
Hi,
It’s pushed to 7.3. It would be good if you and some other committers could spend some time to maybe quickly check to start up solr’s techexample with Java 8, Java 9 and also Java 10 on your favourite operating system.
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen <https://maps.google.com/?q=Achterdiek+19,+D-28357+Bremen&entry=gmail&source=g>
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de <ma...@thetaphi.de>
From: Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> >
Sent: Tuesday, March 27, 2018 10:31 PM
To: dev@lucene.apache.org <ma...@lucene.apache.org>
Subject: Re: Lucene/Solr 7.3
> I think that's what's happening?
Correct - just waiting for SOLR-12141 and I’ll starting building the next RC.
On 27 Mar 2018, at 20:48, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com> > wrote:
I have the 7.3 Ref Guide built locally and the PDF has been pushed to the solr-ref-guide-rc SVN repo, but I'm holding off on starting the vote thread until RC2 of 7.3 is available (I think that's what's happening? please correct me if I've misread the threads) so one vote doesn't finish too far ahead of the other.
Cassandra
On Mon, Mar 26, 2018 at 9:29 AM, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
The release candidate is out, everybody please vote!
I’ve drafted some release notes, available here:
https://wiki.apache.org/solr/ReleaseNote73
https://wiki.apache.org/lucene-java/ReleaseNote73
They’re fairly bare-bones at the moment, if anybody would like to expand on them please feel free.
On 21 Mar 2018, at 15:53, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
FYI I’ve started building a release candidate.
I’ve updated the build script on 7.3 to allow building with ant 1.10, if this doesn’t produce any problems then I’ll forward-port to 7x and master.
On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi Alan,
I committed the fix as well as resolve the issue.
Thanks!
On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
OK, thanks. Let me know when it’s in.
On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi Alan, guys,
I found a blocker issue SOLR-12129, I've already uploaded a patch and beasting the tests, if the result is good I will commit and notify your guys!
Thanks!
On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
Go ahead!
On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.com <ma...@lucidworks.com> > wrote:
Alan,
I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
+1 to backport your fixes
On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in> > wrote:
I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
@Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi guys, Alan
I committed the fix for SOLR-12110 to branch_7_3
Thanks!
On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi Alan,
Sure the issue is marked as Blocker for 7.3.
On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi guys, Alan,
I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
Thanks!
On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
Thanks, Alan
On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
We’re now in feature-freeze for 7.3, so please bear in mind the following:
* No new features may be committed to the branch.
* Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
* All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
* Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
* Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com> > wrote:
I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com> > wrote:
+1
Mike McCandless
http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk> > wrote:
Hi all,
It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
- Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
Re: Lucene/Solr 7.3
Posted by Varun Thacker <va...@vthacker.in>.
Tried running Solr's techproducts example from the 7.3 branch with java
8,9,10 and was able to run it successfully
On Tue, Mar 27, 2018 at 1:56 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
> Hi,
>
>
>
> It’s pushed to 7.3. It would be good if you and some other committers
> could spend some time to maybe quickly check to start up solr’s techexample
> with Java 8, Java 9 and also Java 10 on your favourite operating system.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
> <https://maps.google.com/?q=Achterdiek+19,+D-28357+Bremen&entry=gmail&source=g>
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* Alan Woodward <ro...@gmail.com>
> *Sent:* Tuesday, March 27, 2018 10:31 PM
> *To:* dev@lucene.apache.org
> *Subject:* Re: Lucene/Solr 7.3
>
>
>
> > I think that's what's happening?
>
>
>
> Correct - just waiting for SOLR-12141 and I’ll starting building the next
> RC.
>
>
>
> On 27 Mar 2018, at 20:48, Cassandra Targett <ca...@gmail.com> wrote:
>
>
>
> I have the 7.3 Ref Guide built locally and the PDF has been pushed to the
> solr-ref-guide-rc SVN repo, but I'm holding off on starting the vote thread
> until RC2 of 7.3 is available (I think that's what's happening? please
> correct me if I've misread the threads) so one vote doesn't finish too far
> ahead of the other.
>
>
>
> Cassandra
>
>
>
> On Mon, Mar 26, 2018 at 9:29 AM, Alan Woodward <ro...@gmail.com>
> wrote:
>
> The release candidate is out, everybody please vote!
>
>
>
> I’ve drafted some release notes, available here:
>
> https://wiki.apache.org/solr/ReleaseNote73
>
> https://wiki.apache.org/lucene-java/ReleaseNote73
>
>
>
> They’re fairly bare-bones at the moment, if anybody would like to expand
> on them please feel free.
>
>
>
>
>
> On 21 Mar 2018, at 15:53, Alan Woodward <ro...@gmail.com> wrote:
>
>
>
> FYI I’ve started building a release candidate.
>
>
>
> I’ve updated the build script on 7.3 to allow building with ant 1.10, if
> this doesn’t produce any problems then I’ll forward-port to 7x and master.
>
>
>
> On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
>
>
> Hi Alan,
>
>
>
> I committed the fix as well as resolve the issue.
>
>
>
> Thanks!
>
>
>
> On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <ro...@gmail.com>
> wrote:
>
> OK, thanks. Let me know when it’s in.
>
>
>
>
>
> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
>
>
> Hi Alan, guys,
>
>
>
> I found a blocker issue SOLR-12129, I've already uploaded a patch and
> beasting the tests, if the result is good I will commit and notify your
> guys!
>
>
>
> Thanks!
>
>
>
> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <ro...@gmail.com>
> wrote:
>
> Go ahead!
>
>
>
>
>
> On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.
> com> wrote:
>
>
>
> Alan,
>
>
>
> I would like to commit the change in SOLR-11407 (
> 78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the
> logic that waits for replica recovery and provides more details about any
> failures.
>
>
>
> On 17 Mar 2018, at 13:01, Alan Woodward <ro...@gmail.com> wrote:
>
>
>
> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can
> help debugging that if need be.
>
>
>
> +1 to backport your fixes
>
>
>
> On 17 Mar 2018, at 01:42, Varun Thacker <va...@vthacker.in> wrote:
>
>
>
> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is
> the fix complete for this Andrzej?
>
>
>
> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083
> yesterday and SOLR-12063 today to master/branch_7x. Both are important
> fixes for CDCR so if you are okay I can backport it to the release branch
>
>
>
> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <ca...@gmail.com>
> wrote:
>
> Hi guys, Alan
>
>
>
> I committed the fix for SOLR-12110 to branch_7_3
>
>
>
> Thanks!
>
>
>
> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
> wrote:
>
> Hi Alan,
>
>
>
> Sure the issue is marked as Blocker for 7.3.
>
>
>
> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
> wrote:
>
> Thanks Đạt, could you mark the issue as a Blocker and let me know when
> it’s been resolved?
>
>
>
> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
>
>
> Hi guys, Alan,
>
>
>
> I found a blocker issue SOLR-12110, when investigating test failure. I've
> already uploaded a patch and beasting the tests, if the result is good I
> will commit soon.
>
>
>
> Thanks!
>
>
>
> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
> wrote:
>
> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can
> you give me a hand setting up the 7.3 Jenkins jobs?
>
>
>
> Thanks, Alan
>
>
>
>
>
> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>
>
>
> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes
> and doc patches and then create a release candidate.
>
>
>
> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>
> - No new features may be committed to the branch.
>
>
> - Documentation patches, build patches and serious bug fixes may be
> committed to the branch. However, you should submit *all* patches you
> want to commit to Jira first to give others the chance to review and
> possibly vote against the patch. Keep in mind that it is our main intention
> to keep the branch as stable as possible.
>
>
> - All patches that are intended for the branch should first be
> committed to the unstable branch, merged into the stable branch, and then
> into the current release branch.
> - Normal unstable and stable branch development may continue as usual.
> However, if you plan to commit a big change to the unstable branch while
> the branch feature freeze is in effect, think twice: can't the addition
> wait a couple more days? Merges of bug fixes into the branch may become
> more difficult.
>
>
> - *Only* Jira issues with Fix version “7.3" and priority "Blocker"
> will delay a release candidate build.
>
>
>
>
>
> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>
>
>
> FYI I’m still recovering from my travels, so I’m going to create the
> release branch on Monday instead.
>
>
>
> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com> wrote:
>
>
>
> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts
> RC is ready, so this is a great time to remind folks that if you've got
> Ref Guide changes to be done, you've got a couple weeks. If you're stuck or
> not sure what to do, let me know & I'm happy to help you out.
>
>
>
> Eventually we'd like to release both the Ref Guide and Lucene/Solr with
> the same release process, so this will be a big first test to see how ready
> for that we are.
>
>
>
> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
> lucene@mikemccandless.com> wrote:
>
> +1
>
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
>
> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
> alan.woodward@romseysoftware.co.uk> wrote:
>
> Hi all,
>
> It’s been a couple of months since the 7.2 release, and we’ve accumulated
> some nice new features since then. I’d like to volunteer to be RM for a
> 7.3 release.
>
> I’m travelling for the next couple of weeks, so I would plan to create the
> release branch two weeks today, on the 9th March (unless anybody else wants
> to do it sooner, of course :)
>
> - Alan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
RE: Lucene/Solr 7.3
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
It’s pushed to 7.3. It would be good if you and some other committers could spend some time to maybe quickly check to start up solr’s techexample with Java 8, Java 9 and also Java 10 on your favourite operating system.
Uwe
-----
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: uwe@thetaphi.de
From: Alan Woodward <ro...@gmail.com>
Sent: Tuesday, March 27, 2018 10:31 PM
To: dev@lucene.apache.org
Subject: Re: Lucene/Solr 7.3
> I think that's what's happening?
Correct - just waiting for SOLR-12141 and I’ll starting building the next RC.
On 27 Mar 2018, at 20:48, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com> > wrote:
I have the 7.3 Ref Guide built locally and the PDF has been pushed to the solr-ref-guide-rc SVN repo, but I'm holding off on starting the vote thread until RC2 of 7.3 is available (I think that's what's happening? please correct me if I've misread the threads) so one vote doesn't finish too far ahead of the other.
Cassandra
On Mon, Mar 26, 2018 at 9:29 AM, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
The release candidate is out, everybody please vote!
I’ve drafted some release notes, available here:
https://wiki.apache.org/solr/ReleaseNote73
https://wiki.apache.org/lucene-java/ReleaseNote73
They’re fairly bare-bones at the moment, if anybody would like to expand on them please feel free.
On 21 Mar 2018, at 15:53, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
FYI I’ve started building a release candidate.
I’ve updated the build script on 7.3 to allow building with ant 1.10, if this doesn’t produce any problems then I’ll forward-port to 7x and master.
On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi Alan,
I committed the fix as well as resolve the issue.
Thanks!
On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
OK, thanks. Let me know when it’s in.
On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi Alan, guys,
I found a blocker issue SOLR-12129, I've already uploaded a patch and beasting the tests, if the result is good I will commit and notify your guys!
Thanks!
On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
Go ahead!
On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.com <ma...@lucidworks.com> > wrote:
Alan,
I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
+1 to backport your fixes
On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in> > wrote:
I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
@Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi guys, Alan
I committed the fix for SOLR-12110 to branch_7_3
Thanks!
On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi Alan,
Sure the issue is marked as Blocker for 7.3.
On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com> > wrote:
Hi guys, Alan,
I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
Thanks!
On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
Thanks, Alan
On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
We’re now in feature-freeze for 7.3, so please bear in mind the following:
* No new features may be committed to the branch.
* Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
* All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
* Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
* Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com> > wrote:
FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com> > wrote:
I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com> > wrote:
+1
Mike McCandless
http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk> > wrote:
Hi all,
It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
- Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
> I think that's what's happening?
Correct - just waiting for SOLR-12141 and I’ll starting building the next RC.
> On 27 Mar 2018, at 20:48, Cassandra Targett <ca...@gmail.com> wrote:
>
> I have the 7.3 Ref Guide built locally and the PDF has been pushed to the solr-ref-guide-rc SVN repo, but I'm holding off on starting the vote thread until RC2 of 7.3 is available (I think that's what's happening? please correct me if I've misread the threads) so one vote doesn't finish too far ahead of the other.
>
> Cassandra
>
> On Mon, Mar 26, 2018 at 9:29 AM, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
> The release candidate is out, everybody please vote!
>
> I’ve drafted some release notes, available here:
> https://wiki.apache.org/solr/ReleaseNote73 <https://wiki.apache.org/solr/ReleaseNote73>
> https://wiki.apache.org/lucene-java/ReleaseNote73 <https://wiki.apache.org/lucene-java/ReleaseNote73>
>
> They’re fairly bare-bones at the moment, if anybody would like to expand on them please feel free.
>
>
>> On 21 Mar 2018, at 15:53, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>
>> FYI I’ve started building a release candidate.
>>
>> I’ve updated the build script on 7.3 to allow building with ant 1.10, if this doesn’t produce any problems then I’ll forward-port to 7x and master.
>>
>>> On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi Alan,
>>>
>>> I committed the fix as well as resolve the issue.
>>>
>>> Thanks!
>>>
>>> On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>> OK, thanks. Let me know when it’s in.
>>>
>>>
>>>> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hi Alan, guys,
>>>>
>>>> I found a blocker issue SOLR-12129, I've already uploaded a patch and beasting the tests, if the result is good I will commit and notify your guys!
>>>>
>>>> Thanks!
>>>>
>>>> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>> Go ahead!
>>>>
>>>>
>>>>> On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.com <ma...@lucidworks.com>> wrote:
>>>>>
>>>>> Alan,
>>>>>
>>>>> I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
>>>>>
>>>>>> On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
>>>>>>
>>>>>> +1 to backport your fixes
>>>>>>
>>>>>>> On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
>>>>>>>
>>>>>>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>>>>>>>
>>>>>>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>>>>>>>
>>>>>>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Hi guys, Alan
>>>>>>>
>>>>>>> I committed the fix for SOLR-12110 to branch_7_3
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Hi Alan,
>>>>>>>
>>>>>>> Sure the issue is marked as Blocker for 7.3.
>>>>>>>
>>>>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>>>>>>>
>>>>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> Hi guys, Alan,
>>>>>>>>
>>>>>>>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>>>>
>>>>>>>> Thanks, Alan
>>>>>>>>
>>>>>>>>
>>>>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>>>>>>>
>>>>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>>>>>>>> No new features may be committed to the branch.
>>>>>>>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>>>>>>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>>>>>>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>>>>>>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>
>>>>>>>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>>>>>>>
>>>>>>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>>>>>>>
>>>>>>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> Mike McCandless
>>>>>>>>>>>
>>>>>>>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>>>>>>>
>>>>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>>>>>>>
>>>>>>>>>>> - Alan
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
Re: Lucene/Solr 7.3
Posted by Cassandra Targett <ca...@gmail.com>.
I have the 7.3 Ref Guide built locally and the PDF has been pushed to the
solr-ref-guide-rc SVN repo, but I'm holding off on starting the vote thread
until RC2 of 7.3 is available (I think that's what's happening? please
correct me if I've misread the threads) so one vote doesn't finish too far
ahead of the other.
Cassandra
On Mon, Mar 26, 2018 at 9:29 AM, Alan Woodward <ro...@gmail.com> wrote:
> The release candidate is out, everybody please vote!
>
> I’ve drafted some release notes, available here:
> https://wiki.apache.org/solr/ReleaseNote73
> https://wiki.apache.org/lucene-java/ReleaseNote73
>
> They’re fairly bare-bones at the moment, if anybody would like to expand
> on them please feel free.
>
>
> On 21 Mar 2018, at 15:53, Alan Woodward <ro...@gmail.com> wrote:
>
> FYI I’ve started building a release candidate.
>
> I’ve updated the build script on 7.3 to allow building with ant 1.10, if
> this doesn’t produce any problems then I’ll forward-port to 7x and master.
>
> On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
> Hi Alan,
>
> I committed the fix as well as resolve the issue.
>
> Thanks!
>
> On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <ro...@gmail.com>
> wrote:
>
>> OK, thanks. Let me know when it’s in.
>>
>>
>> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>>
>> Hi Alan, guys,
>>
>> I found a blocker issue SOLR-12129, I've already uploaded a patch and
>> beasting the tests, if the result is good I will commit and notify your
>> guys!
>>
>> Thanks!
>>
>> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <ro...@gmail.com>
>> wrote:
>>
>>> Go ahead!
>>>
>>>
>>> On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.
>>> com> wrote:
>>>
>>> Alan,
>>>
>>> I would like to commit the change in SOLR-11407 (
>>> 78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the
>>> logic that waits for replica recovery and provides more details about any
>>> failures.
>>>
>>> On 17 Mar 2018, at 13:01, Alan Woodward <ro...@gmail.com> wrote:
>>>
>>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can
>>> help debugging that if need be.
>>>
>>> +1 to backport your fixes
>>>
>>> On 17 Mar 2018, at 01:42, Varun Thacker <va...@vthacker.in> wrote:
>>>
>>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is
>>> the fix complete for this Andrzej?
>>>
>>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083
>>> yesterday and SOLR-12063 today to master/branch_7x. Both are important
>>> fixes for CDCR so if you are okay I can backport it to the release branch
>>>
>>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <ca...@gmail.com>
>>> wrote:
>>>
>>>> Hi guys, Alan
>>>>
>>>> I committed the fix for SOLR-12110 to branch_7_3
>>>>
>>>> Thanks!
>>>>
>>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Alan,
>>>>>
>>>>> Sure the issue is marked as Blocker for 7.3.
>>>>>
>>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know
>>>>>> when it’s been resolved?
>>>>>>
>>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi guys, Alan,
>>>>>>
>>>>>> I found a blocker issue SOLR-12110, when investigating test failure.
>>>>>> I've already uploaded a patch and beasting the tests, if the result is good
>>>>>> I will commit soon.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or
>>>>>>> Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>>>
>>>>>>> Thanks, Alan
>>>>>>>
>>>>>>>
>>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for
>>>>>>> bug-fixes and doc patches and then create a release candidate.
>>>>>>>
>>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the
>>>>>>> following:
>>>>>>>
>>>>>>> - No new features may be committed to the branch.
>>>>>>> - Documentation patches, build patches and serious bug fixes may
>>>>>>> be committed to the branch. However, you should submit *all* patches
>>>>>>> you want to commit to Jira first to give others the chance to review and
>>>>>>> possibly vote against the patch. Keep in mind that it is our main intention
>>>>>>> to keep the branch as stable as possible.
>>>>>>> - All patches that are intended for the branch should first be
>>>>>>> committed to the unstable branch, merged into the stable branch, and then
>>>>>>> into the current release branch.
>>>>>>> - Normal unstable and stable branch development may continue as
>>>>>>> usual. However, if you plan to commit a big change to the unstable branch
>>>>>>> while the branch feature freeze is in effect, think twice: can't the
>>>>>>> addition wait a couple more days? Merges of bug fixes into the branch may
>>>>>>> become more difficult.
>>>>>>> - *Only* Jira issues with Fix version “7.3" and priority
>>>>>>> "Blocker" will delay a release candidate build.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>>>>>>
>>>>>>> FYI I’m still recovering from my travels, so I’m going to create the
>>>>>>> release branch on Monday instead.
>>>>>>>
>>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr
>>>>>>> artifacts RC is ready, so this is a great time to remind folks that
>>>>>>> if you've got Ref Guide changes to be done, you've got a couple weeks. If
>>>>>>> you're stuck or not sure what to do, let me know & I'm happy to help you
>>>>>>> out.
>>>>>>>
>>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr
>>>>>>> with the same release process, so this will be a big first test to see how
>>>>>>> ready for that we are.
>>>>>>>
>>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>>>>>>> lucene@mikemccandless.com> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Mike McCandless
>>>>>>>>
>>>>>>>> http://blog.mikemccandless.com
>>>>>>>>
>>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>>>>>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>>>>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>>>>>>> RM for a 7.3 release.
>>>>>>>>>
>>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to
>>>>>>>>> create the release branch two weeks today, on the 9th March (unless anybody
>>>>>>>>> else wants to do it sooner, of course :)
>>>>>>>>>
>>>>>>>>> - Alan
>>>>>>>>> ------------------------------------------------------------
>>>>>>>>> ---------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>
>>>
>>>
>>>
>>
>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
The release candidate is out, everybody please vote!
I’ve drafted some release notes, available here:
https://wiki.apache.org/solr/ReleaseNote73 <https://wiki.apache.org/solr/ReleaseNote73>
https://wiki.apache.org/lucene-java/ReleaseNote73 <https://wiki.apache.org/lucene-java/ReleaseNote73>
They’re fairly bare-bones at the moment, if anybody would like to expand on them please feel free.
> On 21 Mar 2018, at 15:53, Alan Woodward <ro...@gmail.com> wrote:
>
> FYI I’ve started building a release candidate.
>
> I’ve updated the build script on 7.3 to allow building with ant 1.10, if this doesn’t produce any problems then I’ll forward-port to 7x and master.
>
>> On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>
>> Hi Alan,
>>
>> I committed the fix as well as resolve the issue.
>>
>> Thanks!
>>
>> On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>> OK, thanks. Let me know when it’s in.
>>
>>
>>> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi Alan, guys,
>>>
>>> I found a blocker issue SOLR-12129, I've already uploaded a patch and beasting the tests, if the result is good I will commit and notify your guys!
>>>
>>> Thanks!
>>>
>>> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>> Go ahead!
>>>
>>>
>>>> On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.com <ma...@lucidworks.com>> wrote:
>>>>
>>>> Alan,
>>>>
>>>> I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
>>>>
>>>>> On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
>>>>>
>>>>> +1 to backport your fixes
>>>>>
>>>>>> On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
>>>>>>
>>>>>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>>>>>>
>>>>>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>>>>>>
>>>>>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>> Hi guys, Alan
>>>>>>
>>>>>> I committed the fix for SOLR-12110 to branch_7_3
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>> Hi Alan,
>>>>>>
>>>>>> Sure the issue is marked as Blocker for 7.3.
>>>>>>
>>>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>>>>>>
>>>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> Hi guys, Alan,
>>>>>>>
>>>>>>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>>>
>>>>>>> Thanks, Alan
>>>>>>>
>>>>>>>
>>>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>>>>>>
>>>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>>>>>>> No new features may be committed to the branch.
>>>>>>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>>>>>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>>>>>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>>>>>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>>>>>>
>>>>>>>>
>>>>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>>>>>>
>>>>>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>
>>>>>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>>>>>>
>>>>>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> Mike McCandless
>>>>>>>>>>
>>>>>>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>>>>>>
>>>>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>>>>>>
>>>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>>>>>>
>>>>>>>>>> - Alan
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
FYI I’ve started building a release candidate.
I’ve updated the build script on 7.3 to allow building with ant 1.10, if this doesn’t produce any problems then I’ll forward-port to 7x and master.
> On 21 Mar 2018, at 02:37, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
> Hi Alan,
>
> I committed the fix as well as resolve the issue.
>
> Thanks!
>
> On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
> OK, thanks. Let me know when it’s in.
>
>
>> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>
>> Hi Alan, guys,
>>
>> I found a blocker issue SOLR-12129, I've already uploaded a patch and beasting the tests, if the result is good I will commit and notify your guys!
>>
>> Thanks!
>>
>> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>> Go ahead!
>>
>>
>>> On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.com <ma...@lucidworks.com>> wrote:
>>>
>>> Alan,
>>>
>>> I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
>>>
>>>> On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
>>>>
>>>> +1 to backport your fixes
>>>>
>>>>> On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
>>>>>
>>>>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>>>>>
>>>>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>>>>>
>>>>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>> Hi guys, Alan
>>>>>
>>>>> I committed the fix for SOLR-12110 to branch_7_3
>>>>>
>>>>> Thanks!
>>>>>
>>>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>> Hi Alan,
>>>>>
>>>>> Sure the issue is marked as Blocker for 7.3.
>>>>>
>>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>>>>>
>>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi guys, Alan,
>>>>>>
>>>>>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>>
>>>>>> Thanks, Alan
>>>>>>
>>>>>>
>>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>>>>>
>>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>>>>>> No new features may be committed to the branch.
>>>>>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>>>>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>>>>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>>>>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>>>>>
>>>>>>>
>>>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>>>>>
>>>>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>>>>>
>>>>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>>>>>
>>>>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> Mike McCandless
>>>>>>>>>
>>>>>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>>>>>
>>>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>>>>>
>>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>>>>>
>>>>>>>>> - Alan
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Lucene/Solr 7.3
Posted by Đạt Cao Mạnh <ca...@gmail.com>.
Hi Alan,
I committed the fix as well as resolve the issue.
Thanks!
On Tue, Mar 20, 2018 at 9:27 PM Alan Woodward <ro...@gmail.com> wrote:
> OK, thanks. Let me know when it’s in.
>
>
> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
> Hi Alan, guys,
>
> I found a blocker issue SOLR-12129, I've already uploaded a patch and
> beasting the tests, if the result is good I will commit and notify your
> guys!
>
> Thanks!
>
> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <ro...@gmail.com>
> wrote:
>
>> Go ahead!
>>
>>
>> On 19 Mar 2018, at 18:33, Andrzej Białecki <
>> andrzej.bialecki@lucidworks.com> wrote:
>>
>> Alan,
>>
>> I would like to commit the change in SOLR-11407 (
>> 78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the
>> logic that waits for replica recovery and provides more details about any
>> failures.
>>
>> On 17 Mar 2018, at 13:01, Alan Woodward <ro...@gmail.com> wrote:
>>
>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can
>> help debugging that if need be.
>>
>> +1 to backport your fixes
>>
>> On 17 Mar 2018, at 01:42, Varun Thacker <va...@vthacker.in> wrote:
>>
>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is
>> the fix complete for this Andrzej?
>>
>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083
>> yesterday and SOLR-12063 today to master/branch_7x. Both are important
>> fixes for CDCR so if you are okay I can backport it to the release branch
>>
>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <ca...@gmail.com>
>> wrote:
>>
>>> Hi guys, Alan
>>>
>>> I committed the fix for SOLR-12110 to branch_7_3
>>>
>>> Thanks!
>>>
>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
>>> wrote:
>>>
>>>> Hi Alan,
>>>>
>>>> Sure the issue is marked as Blocker for 7.3.
>>>>
>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when
>>>>> it’s been resolved?
>>>>>
>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi guys, Alan,
>>>>>
>>>>> I found a blocker issue SOLR-12110, when investigating test failure.
>>>>> I've already uploaded a patch and beasting the tests, if the result is good
>>>>> I will commit soon.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or
>>>>>> Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>>
>>>>>> Thanks, Alan
>>>>>>
>>>>>>
>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>>>>>>
>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for
>>>>>> bug-fixes and doc patches and then create a release candidate.
>>>>>>
>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the
>>>>>> following:
>>>>>>
>>>>>> - No new features may be committed to the branch.
>>>>>> - Documentation patches, build patches and serious bug fixes may
>>>>>> be committed to the branch. However, you should submit *all* patches
>>>>>> you want to commit to Jira first to give others the chance to review and
>>>>>> possibly vote against the patch. Keep in mind that it is our main intention
>>>>>> to keep the branch as stable as possible.
>>>>>> - All patches that are intended for the branch should first be
>>>>>> committed to the unstable branch, merged into the stable branch, and then
>>>>>> into the current release branch.
>>>>>> - Normal unstable and stable branch development may continue as
>>>>>> usual. However, if you plan to commit a big change to the unstable branch
>>>>>> while the branch feature freeze is in effect, think twice: can't the
>>>>>> addition wait a couple more days? Merges of bug fixes into the branch may
>>>>>> become more difficult.
>>>>>> - *Only* Jira issues with Fix version “7.3" and priority
>>>>>> "Blocker" will delay a release candidate build.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>>>>>
>>>>>> FYI I’m still recovering from my travels, so I’m going to create the
>>>>>> release branch on Monday instead.
>>>>>>
>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr
>>>>>> artifacts RC is ready, so this is a great time to remind folks that
>>>>>> if you've got Ref Guide changes to be done, you've got a couple weeks. If
>>>>>> you're stuck or not sure what to do, let me know & I'm happy to help you
>>>>>> out.
>>>>>>
>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr
>>>>>> with the same release process, so this will be a big first test to see how
>>>>>> ready for that we are.
>>>>>>
>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>>>>>> lucene@mikemccandless.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Mike McCandless
>>>>>>>
>>>>>>> http://blog.mikemccandless.com
>>>>>>>
>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>>>>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>>>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>>>>>> RM for a 7.3 release.
>>>>>>>>
>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to
>>>>>>>> create the release branch two weeks today, on the 9th March (unless anybody
>>>>>>>> else wants to do it sooner, of course :)
>>>>>>>>
>>>>>>>> - Alan
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>>
>>
>>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
OK, thanks. Let me know when it’s in.
> On 20 Mar 2018, at 14:07, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
> Hi Alan, guys,
>
> I found a blocker issue SOLR-12129, I've already uploaded a patch and beasting the tests, if the result is good I will commit and notify your guys!
>
> Thanks!
>
> On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
> Go ahead!
>
>
>> On 19 Mar 2018, at 18:33, Andrzej Białecki <andrzej.bialecki@lucidworks.com <ma...@lucidworks.com>> wrote:
>>
>> Alan,
>>
>> I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
>>
>>> On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
>>>
>>> +1 to backport your fixes
>>>
>>>> On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
>>>>
>>>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>>>>
>>>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>>>>
>>>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>> Hi guys, Alan
>>>>
>>>> I committed the fix for SOLR-12110 to branch_7_3
>>>>
>>>> Thanks!
>>>>
>>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>> Hi Alan,
>>>>
>>>> Sure the issue is marked as Blocker for 7.3.
>>>>
>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>>>>
>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hi guys, Alan,
>>>>>
>>>>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>
>>>>> Thanks, Alan
>>>>>
>>>>>
>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>>>>
>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>>>>> No new features may be committed to the branch.
>>>>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>>>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>>>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>>>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>>>>
>>>>>>
>>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>>>>
>>>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>>>>
>>>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>>>>
>>>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Mike McCandless
>>>>>>>>
>>>>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>>>>
>>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>>>>
>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>>>>
>>>>>>>> - Alan
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Lucene/Solr 7.3
Posted by Đạt Cao Mạnh <ca...@gmail.com>.
Hi Alan, guys,
I found a blocker issue SOLR-12129, I've already uploaded a patch and
beasting the tests, if the result is good I will commit and notify your
guys!
Thanks!
On Tue, Mar 20, 2018 at 2:37 AM Alan Woodward <ro...@gmail.com> wrote:
> Go ahead!
>
>
> On 19 Mar 2018, at 18:33, Andrzej Białecki <
> andrzej.bialecki@lucidworks.com> wrote:
>
> Alan,
>
> I would like to commit the change in SOLR-11407 (
> 78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the
> logic that waits for replica recovery and provides more details about any
> failures.
>
> On 17 Mar 2018, at 13:01, Alan Woodward <ro...@gmail.com> wrote:
>
> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can
> help debugging that if need be.
>
> +1 to backport your fixes
>
> On 17 Mar 2018, at 01:42, Varun Thacker <va...@vthacker.in> wrote:
>
> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is
> the fix complete for this Andrzej?
>
> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083
> yesterday and SOLR-12063 today to master/branch_7x. Both are important
> fixes for CDCR so if you are okay I can backport it to the release branch
>
> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <ca...@gmail.com>
> wrote:
>
>> Hi guys, Alan
>>
>> I committed the fix for SOLR-12110 to branch_7_3
>>
>> Thanks!
>>
>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
>> wrote:
>>
>>> Hi Alan,
>>>
>>> Sure the issue is marked as Blocker for 7.3.
>>>
>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
>>> wrote:
>>>
>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when
>>>> it’s been resolved?
>>>>
>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>>>>
>>>> Hi guys, Alan,
>>>>
>>>> I found a blocker issue SOLR-12110, when investigating test failure.
>>>> I've already uploaded a patch and beasting the tests, if the result is good
>>>> I will commit soon.
>>>>
>>>> Thanks!
>>>>
>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
>>>> wrote:
>>>>
>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve,
>>>>> can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>
>>>>> Thanks, Alan
>>>>>
>>>>>
>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>>>>>
>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for
>>>>> bug-fixes and doc patches and then create a release candidate.
>>>>>
>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the
>>>>> following:
>>>>>
>>>>> - No new features may be committed to the branch.
>>>>> - Documentation patches, build patches and serious bug fixes may
>>>>> be committed to the branch. However, you should submit *all* patches
>>>>> you want to commit to Jira first to give others the chance to review and
>>>>> possibly vote against the patch. Keep in mind that it is our main intention
>>>>> to keep the branch as stable as possible.
>>>>> - All patches that are intended for the branch should first be
>>>>> committed to the unstable branch, merged into the stable branch, and then
>>>>> into the current release branch.
>>>>> - Normal unstable and stable branch development may continue as
>>>>> usual. However, if you plan to commit a big change to the unstable branch
>>>>> while the branch feature freeze is in effect, think twice: can't the
>>>>> addition wait a couple more days? Merges of bug fixes into the branch may
>>>>> become more difficult.
>>>>> - *Only* Jira issues with Fix version “7.3" and priority "Blocker"
>>>>> will delay a release candidate build.
>>>>>
>>>>>
>>>>>
>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>>>>
>>>>> FYI I’m still recovering from my travels, so I’m going to create the
>>>>> release branch on Monday instead.
>>>>>
>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr
>>>>> artifacts RC is ready, so this is a great time to remind folks that
>>>>> if you've got Ref Guide changes to be done, you've got a couple weeks. If
>>>>> you're stuck or not sure what to do, let me know & I'm happy to help you
>>>>> out.
>>>>>
>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr
>>>>> with the same release process, so this will be a big first test to see how
>>>>> ready for that we are.
>>>>>
>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>>>>> lucene@mikemccandless.com> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Mike McCandless
>>>>>>
>>>>>> http://blog.mikemccandless.com
>>>>>>
>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>>>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>>>>> RM for a 7.3 release.
>>>>>>>
>>>>>>> I’m travelling for the next couple of weeks, so I would plan to
>>>>>>> create the release branch two weeks today, on the 9th March (unless anybody
>>>>>>> else wants to do it sooner, of course :)
>>>>>>>
>>>>>>> - Alan
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>
>
>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
Go ahead!
> On 19 Mar 2018, at 18:33, Andrzej Białecki <an...@lucidworks.com> wrote:
>
> Alan,
>
> I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
>
>> On 17 Mar 2018, at 13:01, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>
>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
>>
>> +1 to backport your fixes
>>
>>> On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
>>>
>>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>>>
>>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>>>
>>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>> Hi guys, Alan
>>>
>>> I committed the fix for SOLR-12110 to branch_7_3
>>>
>>> Thanks!
>>>
>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>> Hi Alan,
>>>
>>> Sure the issue is marked as Blocker for 7.3.
>>>
>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>>>
>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hi guys, Alan,
>>>>
>>>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>>>
>>>> Thanks!
>>>>
>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>
>>>> Thanks, Alan
>>>>
>>>>
>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>>>
>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>>>> No new features may be committed to the branch.
>>>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>>>
>>>>>
>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>>>
>>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>>>
>>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>>>
>>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>>>> +1
>>>>>>>
>>>>>>> Mike McCandless
>>>>>>>
>>>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>>>
>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>>>
>>>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>>>
>>>>>>> - Alan
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
Re: Lucene/Solr 7.3
Posted by Andrzej Białecki <an...@lucidworks.com>.
Alan,
I would like to commit the change in SOLR-11407 (78d592d2fdfc64c227fc1bcb8fafa3d806fbb384) to branch_7_3. This fixes the logic that waits for replica recovery and provides more details about any failures.
> On 17 Mar 2018, at 13:01, Alan Woodward <ro...@gmail.com> wrote:
>
> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
>
> +1 to backport your fixes
>
>> On 17 Mar 2018, at 01:42, Varun Thacker <varun@vthacker.in <ma...@vthacker.in>> wrote:
>>
>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>>
>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>>
>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>> Hi guys, Alan
>>
>> I committed the fix for SOLR-12110 to branch_7_3
>>
>> Thanks!
>>
>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>> Hi Alan,
>>
>> Sure the issue is marked as Blocker for 7.3.
>>
>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>>
>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi guys, Alan,
>>>
>>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>>
>>> Thanks!
>>>
>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>
>>> Thanks, Alan
>>>
>>>
>>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>>
>>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>>> No new features may be committed to the branch.
>>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>>
>>>>
>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>>
>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>>
>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>>
>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>>> +1
>>>>>>
>>>>>> Mike McCandless
>>>>>>
>>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>>
>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>>
>>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>>
>>>>>> - Alan
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>
Re: Lucene/Solr 7.3
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
Hi Alan,
I found a bug in SOLR-11648 where the cluster suggestions menu item is
visible in standalone Solr mode as well. The fix is trivial and I'll commit
it to 7.3.
On Mon, Mar 19, 2018 at 12:29 AM, Varun Thacker <va...@vthacker.in> wrote:
> Thanks Alan!
>
> On Sat, Mar 17, 2018 at 5:01 AM, Alan Woodward <ro...@gmail.com>
> wrote:
>
>> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can
>> help debugging that if need be.
>>
>> +1 to backport your fixes
>>
>
> Done
>
>>
>>
>> On 17 Mar 2018, at 01:42, Varun Thacker <va...@vthacker.in> wrote:
>>
>> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is
>> the fix complete for this Andrzej?
>>
>> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083
>> yesterday and SOLR-12063 today to master/branch_7x. Both are important
>> fixes for CDCR so if you are okay I can backport it to the release branch
>>
>> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <ca...@gmail.com>
>> wrote:
>>
>>> Hi guys, Alan
>>>
>>> I committed the fix for SOLR-12110 to branch_7_3
>>>
>>> Thanks!
>>>
>>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
>>> wrote:
>>>
>>>> Hi Alan,
>>>>
>>>> Sure the issue is marked as Blocker for 7.3.
>>>>
>>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when
>>>>> it’s been resolved?
>>>>>
>>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi guys, Alan,
>>>>>
>>>>> I found a blocker issue SOLR-12110, when investigating test failure.
>>>>> I've already uploaded a patch and beasting the tests, if the result is good
>>>>> I will commit soon.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or
>>>>>> Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>>
>>>>>> Thanks, Alan
>>>>>>
>>>>>>
>>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>>>>>>
>>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for
>>>>>> bug-fixes and doc patches and then create a release candidate.
>>>>>>
>>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the
>>>>>> following:
>>>>>>
>>>>>> - No new features may be committed to the branch.
>>>>>> - Documentation patches, build patches and serious bug fixes may
>>>>>> be committed to the branch. However, you should submit *all* patches
>>>>>> you want to commit to Jira first to give others the chance to review and
>>>>>> possibly vote against the patch. Keep in mind that it is our main intention
>>>>>> to keep the branch as stable as possible.
>>>>>> - All patches that are intended for the branch should first be
>>>>>> committed to the unstable branch, merged into the stable branch, and then
>>>>>> into the current release branch.
>>>>>> - Normal unstable and stable branch development may continue as
>>>>>> usual. However, if you plan to commit a big change to the unstable branch
>>>>>> while the branch feature freeze is in effect, think twice: can't the
>>>>>> addition wait a couple more days? Merges of bug fixes into the branch may
>>>>>> become more difficult.
>>>>>> - *Only* Jira issues with Fix version “7.3" and priority
>>>>>> "Blocker" will delay a release candidate build.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>>>>>
>>>>>> FYI I’m still recovering from my travels, so I’m going to create the
>>>>>> release branch on Monday instead.
>>>>>>
>>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr
>>>>>> artifacts RC is ready, so this is a great time to remind folks that
>>>>>> if you've got Ref Guide changes to be done, you've got a couple weeks. If
>>>>>> you're stuck or not sure what to do, let me know & I'm happy to help you
>>>>>> out.
>>>>>>
>>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr
>>>>>> with the same release process, so this will be a big first test to see how
>>>>>> ready for that we are.
>>>>>>
>>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>>>>>> lucene@mikemccandless.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Mike McCandless
>>>>>>>
>>>>>>> http://blog.mikemccandless.com
>>>>>>>
>>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>>>>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>>>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>>>>>> RM for a 7.3 release.
>>>>>>>>
>>>>>>>> I’m travelling for the next couple of weeks, so I would plan to
>>>>>>>> create the release branch two weeks today, on the 9th March (unless anybody
>>>>>>>> else wants to do it sooner, of course :)
>>>>>>>>
>>>>>>>> - Alan
>>>>>>>> ------------------------------------------------------------
>>>>>>>> ---------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>>
>
--
Regards,
Shalin Shekhar Mangar.
Re: Lucene/Solr 7.3
Posted by Varun Thacker <va...@vthacker.in>.
Thanks Alan!
On Sat, Mar 17, 2018 at 5:01 AM, Alan Woodward <ro...@gmail.com> wrote:
> I’d like to build the RC on Monday, but it depends on SOLR-12070. I can
> help debugging that if need be.
>
> +1 to backport your fixes
>
Done
>
>
> On 17 Mar 2018, at 01:42, Varun Thacker <va...@vthacker.in> wrote:
>
> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is
> the fix complete for this Andrzej?
>
> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083
> yesterday and SOLR-12063 today to master/branch_7x. Both are important
> fixes for CDCR so if you are okay I can backport it to the release branch
>
> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <ca...@gmail.com>
> wrote:
>
>> Hi guys, Alan
>>
>> I committed the fix for SOLR-12110 to branch_7_3
>>
>> Thanks!
>>
>> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
>> wrote:
>>
>>> Hi Alan,
>>>
>>> Sure the issue is marked as Blocker for 7.3.
>>>
>>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
>>> wrote:
>>>
>>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when
>>>> it’s been resolved?
>>>>
>>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>>>>
>>>> Hi guys, Alan,
>>>>
>>>> I found a blocker issue SOLR-12110, when investigating test failure.
>>>> I've already uploaded a patch and beasting the tests, if the result is good
>>>> I will commit soon.
>>>>
>>>> Thanks!
>>>>
>>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
>>>> wrote:
>>>>
>>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve,
>>>>> can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>>
>>>>> Thanks, Alan
>>>>>
>>>>>
>>>>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>>>>>
>>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for
>>>>> bug-fixes and doc patches and then create a release candidate.
>>>>>
>>>>> We’re now in feature-freeze for 7.3, so please bear in mind the
>>>>> following:
>>>>>
>>>>> - No new features may be committed to the branch.
>>>>> - Documentation patches, build patches and serious bug fixes may
>>>>> be committed to the branch. However, you should submit *all* patches
>>>>> you want to commit to Jira first to give others the chance to review and
>>>>> possibly vote against the patch. Keep in mind that it is our main intention
>>>>> to keep the branch as stable as possible.
>>>>> - All patches that are intended for the branch should first be
>>>>> committed to the unstable branch, merged into the stable branch, and then
>>>>> into the current release branch.
>>>>> - Normal unstable and stable branch development may continue as
>>>>> usual. However, if you plan to commit a big change to the unstable branch
>>>>> while the branch feature freeze is in effect, think twice: can't the
>>>>> addition wait a couple more days? Merges of bug fixes into the branch may
>>>>> become more difficult.
>>>>> - *Only* Jira issues with Fix version “7.3" and priority "Blocker"
>>>>> will delay a release candidate build.
>>>>>
>>>>>
>>>>>
>>>>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>>>>
>>>>> FYI I’m still recovering from my travels, so I’m going to create the
>>>>> release branch on Monday instead.
>>>>>
>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr
>>>>> artifacts RC is ready, so this is a great time to remind folks that
>>>>> if you've got Ref Guide changes to be done, you've got a couple weeks. If
>>>>> you're stuck or not sure what to do, let me know & I'm happy to help you
>>>>> out.
>>>>>
>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr
>>>>> with the same release process, so this will be a big first test to see how
>>>>> ready for that we are.
>>>>>
>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>>>>> lucene@mikemccandless.com> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Mike McCandless
>>>>>>
>>>>>> http://blog.mikemccandless.com
>>>>>>
>>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>>>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>>>>> RM for a 7.3 release.
>>>>>>>
>>>>>>> I’m travelling for the next couple of weeks, so I would plan to
>>>>>>> create the release branch two weeks today, on the 9th March (unless anybody
>>>>>>> else wants to do it sooner, of course :)
>>>>>>>
>>>>>>> - Alan
>>>>>>> ------------------------------------------------------------
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
I’d like to build the RC on Monday, but it depends on SOLR-12070. I can help debugging that if need be.
+1 to backport your fixes
> On 17 Mar 2018, at 01:42, Varun Thacker <va...@vthacker.in> wrote:
>
> I was going through the blockers for 7.3 and only SOLR-12070 came up. Is the fix complete for this Andrzej?
>
> @Alan : When do you plan on cutting an RC ? I committed SOLR-12083 yesterday and SOLR-12063 today to master/branch_7x. Both are important fixes for CDCR so if you are okay I can backport it to the release branch
>
> On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
> Hi guys, Alan
>
> I committed the fix for SOLR-12110 to branch_7_3
>
> Thanks!
>
> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
> Hi Alan,
>
> Sure the issue is marked as Blocker for 7.3.
>
> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
> Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
>
>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>>
>> Hi guys, Alan,
>>
>> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>>
>> Thanks!
>>
>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>>
>> Thanks, Alan
>>
>>
>>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>>
>>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>> No new features may be committed to the branch.
>>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>>
>>>
>>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>>
>>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>>
>>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>>
>>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>>> +1
>>>>>
>>>>> Mike McCandless
>>>>>
>>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>>
>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>>> Hi all,
>>>>>
>>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>>
>>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>>
>>>>> - Alan
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
>
Re: Lucene/Solr 7.3
Posted by Varun Thacker <va...@vthacker.in>.
I was going through the blockers for 7.3 and only SOLR-12070 came up. Is
the fix complete for this Andrzej?
@Alan : When do you plan on cutting an RC ? I committed SOLR-12083
yesterday and SOLR-12063 today to master/branch_7x. Both are important
fixes for CDCR so if you are okay I can backport it to the release branch
On Fri, Mar 16, 2018 at 4:58 PM, Đạt Cao Mạnh <ca...@gmail.com>
wrote:
> Hi guys, Alan
>
> I committed the fix for SOLR-12110 to branch_7_3
>
> Thanks!
>
> On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
> wrote:
>
>> Hi Alan,
>>
>> Sure the issue is marked as Blocker for 7.3.
>>
>> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
>> wrote:
>>
>>> Thanks Đạt, could you mark the issue as a Blocker and let me know when
>>> it’s been resolved?
>>>
>>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>>>
>>> Hi guys, Alan,
>>>
>>> I found a blocker issue SOLR-12110, when investigating test failure.
>>> I've already uploaded a patch and beasting the tests, if the result is good
>>> I will commit soon.
>>>
>>> Thanks!
>>>
>>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
>>> wrote:
>>>
>>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve,
>>>> can you give me a hand setting up the 7.3 Jenkins jobs?
>>>>
>>>> Thanks, Alan
>>>>
>>>>
>>>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>>>>
>>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes
>>>> and doc patches and then create a release candidate.
>>>>
>>>> We’re now in feature-freeze for 7.3, so please bear in mind the
>>>> following:
>>>>
>>>> - No new features may be committed to the branch.
>>>> - Documentation patches, build patches and serious bug fixes may be
>>>> committed to the branch. However, you should submit *all* patches
>>>> you want to commit to Jira first to give others the chance to review and
>>>> possibly vote against the patch. Keep in mind that it is our main intention
>>>> to keep the branch as stable as possible.
>>>> - All patches that are intended for the branch should first be
>>>> committed to the unstable branch, merged into the stable branch, and then
>>>> into the current release branch.
>>>> - Normal unstable and stable branch development may continue as
>>>> usual. However, if you plan to commit a big change to the unstable branch
>>>> while the branch feature freeze is in effect, think twice: can't the
>>>> addition wait a couple more days? Merges of bug fixes into the branch may
>>>> become more difficult.
>>>> - *Only* Jira issues with Fix version “7.3" and priority "Blocker"
>>>> will delay a release candidate build.
>>>>
>>>>
>>>>
>>>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>>>
>>>> FYI I’m still recovering from my travels, so I’m going to create the
>>>> release branch on Monday instead.
>>>>
>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>>>> wrote:
>>>>
>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr
>>>> artifacts RC is ready, so this is a great time to remind folks that if
>>>> you've got Ref Guide changes to be done, you've got a couple weeks. If
>>>> you're stuck or not sure what to do, let me know & I'm happy to help you
>>>> out.
>>>>
>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with
>>>> the same release process, so this will be a big first test to see how ready
>>>> for that we are.
>>>>
>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>>>> lucene@mikemccandless.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> Mike McCandless
>>>>>
>>>>> http://blog.mikemccandless.com
>>>>>
>>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>>>> RM for a 7.3 release.
>>>>>>
>>>>>> I’m travelling for the next couple of weeks, so I would plan to
>>>>>> create the release branch two weeks today, on the 9th March (unless anybody
>>>>>> else wants to do it sooner, of course :)
>>>>>>
>>>>>> - Alan
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
Re: Lucene/Solr 7.3
Posted by Đạt Cao Mạnh <ca...@gmail.com>.
Hi guys, Alan
I committed the fix for SOLR-12110 to branch_7_3
Thanks!
On Fri, Mar 16, 2018 at 5:43 PM Đạt Cao Mạnh <ca...@gmail.com>
wrote:
> Hi Alan,
>
> Sure the issue is marked as Blocker for 7.3.
>
> On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com>
> wrote:
>
>> Thanks Đạt, could you mark the issue as a Blocker and let me know when
>> it’s been resolved?
>>
>> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>>
>> Hi guys, Alan,
>>
>> I found a blocker issue SOLR-12110, when investigating test failure. I've
>> already uploaded a patch and beasting the tests, if the result is good I
>> will commit soon.
>>
>> Thanks!
>>
>> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
>> wrote:
>>
>>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve,
>>> can you give me a hand setting up the 7.3 Jenkins jobs?
>>>
>>> Thanks, Alan
>>>
>>>
>>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>>>
>>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes
>>> and doc patches and then create a release candidate.
>>>
>>> We’re now in feature-freeze for 7.3, so please bear in mind the
>>> following:
>>>
>>> - No new features may be committed to the branch.
>>> - Documentation patches, build patches and serious bug fixes may be
>>> committed to the branch. However, you should submit *all* patches
>>> you want to commit to Jira first to give others the chance to review and
>>> possibly vote against the patch. Keep in mind that it is our main intention
>>> to keep the branch as stable as possible.
>>> - All patches that are intended for the branch should first be
>>> committed to the unstable branch, merged into the stable branch, and then
>>> into the current release branch.
>>> - Normal unstable and stable branch development may continue as
>>> usual. However, if you plan to commit a big change to the unstable branch
>>> while the branch feature freeze is in effect, think twice: can't the
>>> addition wait a couple more days? Merges of bug fixes into the branch may
>>> become more difficult.
>>> - *Only* Jira issues with Fix version “7.3" and priority "Blocker"
>>> will delay a release candidate build.
>>>
>>>
>>>
>>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>>
>>> FYI I’m still recovering from my travels, so I’m going to create the
>>> release branch on Monday instead.
>>>
>>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>>> wrote:
>>>
>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts
>>> RC is ready, so this is a great time to remind folks that if you've got
>>> Ref Guide changes to be done, you've got a couple weeks. If you're stuck or
>>> not sure what to do, let me know & I'm happy to help you out.
>>>
>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with
>>> the same release process, so this will be a big first test to see how ready
>>> for that we are.
>>>
>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>>> lucene@mikemccandless.com> wrote:
>>>
>>>> +1
>>>>
>>>> Mike McCandless
>>>>
>>>> http://blog.mikemccandless.com
>>>>
>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>>> RM for a 7.3 release.
>>>>>
>>>>> I’m travelling for the next couple of weeks, so I would plan to create
>>>>> the release branch two weeks today, on the 9th March (unless anybody else
>>>>> wants to do it sooner, of course :)
>>>>>
>>>>> - Alan
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>>
>>
Re: Lucene/Solr 7.3
Posted by Đạt Cao Mạnh <ca...@gmail.com>.
Hi Alan,
Sure the issue is marked as Blocker for 7.3.
On Fri, Mar 16, 2018 at 3:12 PM Alan Woodward <ro...@gmail.com> wrote:
> Thanks Đạt, could you mark the issue as a Blocker and let me know when
> it’s been resolved?
>
> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <ca...@gmail.com> wrote:
>
> Hi guys, Alan,
>
> I found a blocker issue SOLR-12110, when investigating test failure. I've
> already uploaded a patch and beasting the tests, if the result is good I
> will commit soon.
>
> Thanks!
>
> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com>
> wrote:
>
>> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve,
>> can you give me a hand setting up the 7.3 Jenkins jobs?
>>
>> Thanks, Alan
>>
>>
>> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>>
>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes
>> and doc patches and then create a release candidate.
>>
>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>>
>> - No new features may be committed to the branch.
>> - Documentation patches, build patches and serious bug fixes may be
>> committed to the branch. However, you should submit *all* patches you
>> want to commit to Jira first to give others the chance to review and
>> possibly vote against the patch. Keep in mind that it is our main intention
>> to keep the branch as stable as possible.
>> - All patches that are intended for the branch should first be
>> committed to the unstable branch, merged into the stable branch, and then
>> into the current release branch.
>> - Normal unstable and stable branch development may continue as
>> usual. However, if you plan to commit a big change to the unstable branch
>> while the branch feature freeze is in effect, think twice: can't the
>> addition wait a couple more days? Merges of bug fixes into the branch may
>> become more difficult.
>> - *Only* Jira issues with Fix version “7.3" and priority "Blocker"
>> will delay a release candidate build.
>>
>>
>>
>> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>>
>> FYI I’m still recovering from my travels, so I’m going to create the
>> release branch on Monday instead.
>>
>> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com>
>> wrote:
>>
>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts
>> RC is ready, so this is a great time to remind folks that if you've got
>> Ref Guide changes to be done, you've got a couple weeks. If you're stuck or
>> not sure what to do, let me know & I'm happy to help you out.
>>
>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with
>> the same release process, so this will be a big first test to see how ready
>> for that we are.
>>
>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
>> lucene@mikemccandless.com> wrote:
>>
>>> +1
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com
>>>
>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>>> alan.woodward@romseysoftware.co.uk> wrote:
>>>
>>>> Hi all,
>>>>
>>>> It’s been a couple of months since the 7.2 release, and we’ve
>>>> accumulated some nice new features since then. I’d like to volunteer to be
>>>> RM for a 7.3 release.
>>>>
>>>> I’m travelling for the next couple of weeks, so I would plan to create
>>>> the release branch two weeks today, on the 9th March (unless anybody else
>>>> wants to do it sooner, of course :)
>>>>
>>>> - Alan
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>
>>
>>
>>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
Thanks Đạt, could you mark the issue as a Blocker and let me know when it’s been resolved?
> On 16 Mar 2018, at 02:05, Đạt Cao Mạnh <caomanhdat317@gmail.com <ma...@gmail.com>> wrote:
>
> Hi guys, Alan,
>
> I found a blocker issue SOLR-12110, when investigating test failure. I've already uploaded a patch and beasting the tests, if the result is good I will commit soon.
>
> Thanks!
>
> On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
>
> Thanks, Alan
>
>
>> On 12 Mar 2018, at 09:32, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>
>> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>>
>> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>> No new features may be committed to the branch.
>> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
>> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
>> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
>> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>>
>>
>>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>>
>>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>>
>>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>>
>>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>>> +1
>>>>
>>>> Mike McCandless
>>>>
>>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>>
>>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>>> Hi all,
>>>>
>>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>>
>>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>>
>>>> - Alan
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>>
>>>>
>>>>
>>>
>>
>
Re: Lucene/Solr 7.3
Posted by Đạt Cao Mạnh <ca...@gmail.com>.
Hi guys, Alan,
I found a blocker issue SOLR-12110, when investigating test failure. I've
already uploaded a patch and beasting the tests, if the result is good I
will commit soon.
Thanks!
On Tue, Mar 13, 2018 at 7:49 PM Alan Woodward <ro...@gmail.com> wrote:
> Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can
> you give me a hand setting up the 7.3 Jenkins jobs?
>
> Thanks, Alan
>
>
> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>
> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes
> and doc patches and then create a release candidate.
>
> We’re now in feature-freeze for 7.3, so please bear in mind the following:
>
> - No new features may be committed to the branch.
> - Documentation patches, build patches and serious bug fixes may be
> committed to the branch. However, you should submit *all* patches you
> want to commit to Jira first to give others the chance to review and
> possibly vote against the patch. Keep in mind that it is our main intention
> to keep the branch as stable as possible.
> - All patches that are intended for the branch should first be
> committed to the unstable branch, merged into the stable branch, and then
> into the current release branch.
> - Normal unstable and stable branch development may continue as usual.
> However, if you plan to commit a big change to the unstable branch while
> the branch feature freeze is in effect, think twice: can't the addition
> wait a couple more days? Merges of bug fixes into the branch may become
> more difficult.
> - *Only* Jira issues with Fix version “7.3" and priority "Blocker"
> will delay a release candidate build.
>
>
>
> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>
> FYI I’m still recovering from my travels, so I’m going to create the
> release branch on Monday instead.
>
> On 27 Feb 2018, at 18:51, Cassandra Targett <ca...@gmail.com> wrote:
>
> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts
> RC is ready, so this is a great time to remind folks that if you've got
> Ref Guide changes to be done, you've got a couple weeks. If you're stuck or
> not sure what to do, let me know & I'm happy to help you out.
>
> Eventually we'd like to release both the Ref Guide and Lucene/Solr with
> the same release process, so this will be a big first test to see how ready
> for that we are.
>
> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
> lucene@mikemccandless.com> wrote:
>
>> +1
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
>> alan.woodward@romseysoftware.co.uk> wrote:
>>
>>> Hi all,
>>>
>>> It’s been a couple of months since the 7.2 release, and we’ve
>>> accumulated some nice new features since then. I’d like to volunteer to be
>>> RM for a 7.3 release.
>>>
>>> I’m travelling for the next couple of weeks, so I would plan to create
>>> the release branch two weeks today, on the 9th March (unless anybody else
>>> wants to do it sooner, of course :)
>>>
>>> - Alan
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>
>
>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
Just realised that I don’t have an ASF Jenkins account - Uwe or Steve, can you give me a hand setting up the 7.3 Jenkins jobs?
Thanks, Alan
> On 12 Mar 2018, at 09:32, Alan Woodward <ro...@gmail.com> wrote:
>
> I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
>
> We’re now in feature-freeze for 7.3, so please bear in mind the following:
> No new features may be committed to the branch.
> Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
> All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
> Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
> Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
>
>
>> On 9 Mar 2018, at 16:43, Alan Woodward <romseygeek@gmail.com <ma...@gmail.com>> wrote:
>>
>> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>>
>>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>>
>>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>>
>>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>>> +1
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>>
>>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>>> Hi all,
>>>
>>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>>
>>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>>
>>> - Alan
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>>
>>>
>>>
>>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
I’ve created the 7.3 release branch. I’ll leave 24 hours for bug-fixes and doc patches and then create a release candidate.
We’re now in feature-freeze for 7.3, so please bear in mind the following:
No new features may be committed to the branch.
Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should submit all patches you want to commit to Jira first to give others the chance to review and possibly vote against the patch. Keep in mind that it is our main intention to keep the branch as stable as possible.
All patches that are intended for the branch should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch.
Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult.
Only Jira issues with Fix version “7.3" and priority "Blocker" will delay a release candidate build.
> On 9 Mar 2018, at 16:43, Alan Woodward <ro...@gmail.com> wrote:
>
> FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
>
>> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>>
>> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>>
>> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>>
>> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
>> +1
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>>
>> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
>> Hi all,
>>
>> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>>
>> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>>
>> - Alan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
>> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>>
>>
>>
>
Re: Lucene/Solr 7.3
Posted by Alan Woodward <ro...@gmail.com>.
FYI I’m still recovering from my travels, so I’m going to create the release branch on Monday instead.
> On 27 Feb 2018, at 18:51, Cassandra Targett <casstargett@gmail.com <ma...@gmail.com>> wrote:
>
> I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC is ready, so this is a great time to remind folks that if you've got Ref Guide changes to be done, you've got a couple weeks. If you're stuck or not sure what to do, let me know & I'm happy to help you out.
>
> Eventually we'd like to release both the Ref Guide and Lucene/Solr with the same release process, so this will be a big first test to see how ready for that we are.
>
> On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <lucene@mikemccandless.com <ma...@mikemccandless.com>> wrote:
> +1
>
> Mike McCandless
>
> http://blog.mikemccandless.com <http://blog.mikemccandless.com/>
>
> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <alan.woodward@romseysoftware.co.uk <ma...@romseysoftware.co.uk>> wrote:
> Hi all,
>
> It’s been a couple of months since the 7.2 release, and we’ve accumulated some nice new features since then. I’d like to volunteer to be RM for a 7.3 release.
>
> I’m travelling for the next couple of weeks, so I would plan to create the release branch two weeks today, on the 9th March (unless anybody else wants to do it sooner, of course :)
>
> - Alan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org <ma...@lucene.apache.org>
> For additional commands, e-mail: dev-help@lucene.apache.org <ma...@lucene.apache.org>
>
>
>
Re: Lucene/Solr 7.3
Posted by Cassandra Targett <ca...@gmail.com>.
I intend to create the Ref Guide RC as soon as the Lucene/Solr artifacts RC
is ready, so this is a great time to remind folks that if you've got Ref
Guide changes to be done, you've got a couple weeks. If you're stuck or not
sure what to do, let me know & I'm happy to help you out.
Eventually we'd like to release both the Ref Guide and Lucene/Solr with the
same release process, so this will be a big first test to see how ready for
that we are.
On Tue, Feb 27, 2018 at 11:42 AM, Michael McCandless <
lucene@mikemccandless.com> wrote:
> +1
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
> alan.woodward@romseysoftware.co.uk> wrote:
>
>> Hi all,
>>
>> It’s been a couple of months since the 7.2 release, and we’ve accumulated
>> some nice new features since then. I’d like to volunteer to be RM for a
>> 7.3 release.
>>
>> I’m travelling for the next couple of weeks, so I would plan to create
>> the release branch two weeks today, on the 9th March (unless anybody else
>> wants to do it sooner, of course :)
>>
>> - Alan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Lucene/Solr 7.3
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1
Mike McCandless
http://blog.mikemccandless.com
On Fri, Feb 23, 2018 at 4:50 AM, Alan Woodward <
alan.woodward@romseysoftware.co.uk> wrote:
> Hi all,
>
> It’s been a couple of months since the 7.2 release, and we’ve accumulated
> some nice new features since then. I’d like to volunteer to be RM for a
> 7.3 release.
>
> I’m travelling for the next couple of weeks, so I would plan to create the
> release branch two weeks today, on the 9th March (unless anybody else wants
> to do it sooner, of course :)
>
> - Alan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>