Re: Commit / Code Review Policy

[David Smiley]

(Renamed; no other changes)
https://cwiki.apache.org/confluence/display/LUCENE/Commit+Process+Guidelines

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Wed, Mar 4, 2020 at 8:36 AM Daniel Ruggeri  wrote:

> Hi, all;
> I could have *sworn* I replied... but could find no record in my sent
> folder when David dutifully followed up with a ping. *facepalm*
>
> Yes, I volunteered to participate and help where I can as a member of The
> ASF board, VP Fundraising, ComDev participant, or whatever hat I might be
> able to bring with me. Of course, I bear no special credentials here... we
> all hang out as volunteers. Reviewing the most recent board report[1], I
> detected:
> > We're discussing how to semi-require code reviews by defining project
> guidelines. We invite a board member to help/advice how to navigate this
> balance.
> So, yeah, here I am :-) My primary interest is to be sure we're
> approaching the discussion with community as our primary lens.
>
> I definitely reviewed the email thread, replies, and Confluence wiki
> document. In my interpretation of the discussion, a few things stood out:
> - There were some synchronous discussions that occurred off the list,
> which can lead to accidentally excluding important community voices from
> the conversation. By bringing the discussion back to the list before
> attempting to make a decision, the critical levels of transparency are
> maintained. This is definitely A Good Thing.
> - I perceived a lot of constructive feedback on the initial draft which
> appears (to me) to have brought the draft much closer to a document that
> represents consensus. Said another way, I don't detect conflict per se
> (please correct me if I'm wrong)
> - I think the feedback (and subsequent incorporation of that feedback into
> the guidelines) about exception cases like doc fixes and "small" changes is
> brilliant. On the httpd project, as a parallel example, we have a RTC
> policy for release branches except for docs - which are CTR. Indeed, a
> "docs committer" is the same as an "httpd committer"... we don't separate
> privileges because this social contract has worked well for 2 decades.
> - The current content of the document seems reasonable given the current
> environment. One thing that is unclear to me based on a quick browsing of
> the docs is what the branching strategy is for the project. What I gather
> is that the master branch is the release branch and features are added to
> master or merged in from short-lived feature branches. It'd be helpful to
> clarify this.
> - The proposed document draws additional parallels to things that work for
> httpd. Often times, we will share patches to the list for feedback before
> commits (similar to the Jira tickets proposed). We also operate trunk as
> CTR, but require 3 +1 backport votes to the long-lived release branches.
> This proposal has a similar net effect: bits that get released are
> (generally) intended to be "actively" reviewed before commit. It does fall
> short of requiring a consensus-style vote for release branches as httpd
> does... but that's OK.
>
> All told, this proposal seems quite reasonable to me because it has been
> discussed by the community, feedback has been incorporated, and the content
> of the proposal seems totally doable. That said, I'm open to other
> inquiries if there's something an external perspective can provide. How can
> I help?
>
>
> [1] https://whimsy.apache.org/board/minutes/Lucene.html
>
> P.S.
> Nabble, mbox, etc... they're OK, but have you tried Ponymail?
>
> https://lists.apache.org/x/thread.html/770ef83a8ed3a3d5d161c4a2cd812b4bdde47464d439c09ec31164dd@%3Cdev.lucene.apache.org%3E
> I'm a convert, for sure!
> --
> Daniel Ruggeri
> Director, VP Fundraising, member, httpd PMC
> The Apache Software Foundation
>
> On February 7, 2020 9:14:37 AM CST, David Smiley 
> wrote:
>>
>> I neglected to try and close up this long thread on the subject of code
>> review guidance.  In the project's board report to the ASF, I asked for
>> help; Daniel Ruggeri (an ASF VP) graciously volunteered.  He's on the "To"
>> line to my message here; he's not a member of our dev list.
>>
>> Daniel:
>>
>> Thanks in advance for any assistance / guidance you have to offer.
>>
>> I suggest first reading through this thread:
>>
>> https://lucene.472066.n3.nabble.com/Commit-Code-Review-Policy-td4452928.html
>> I find Nabble much easier to navigate than the ASF official archive, but
>> that's here if you prefer:
>> http://mail-archives.apache.org/mod_mbox/lucene-dev/201911.mbox/%3ccabewpvet1u4xgxqadddhes+uybexmuw33c8fbs5bzdlzulc...@mail.gmail.com%3e
>>   It starts November 26th and ended December 8th.
>>
>> The second thing is my proposal document stored in Confluence.  I have
>> yet to rename it as I said I would but I'll let it be for a little bit so
>> the links continue to work for the moment:
>> 

Re: 2020-03 Committer virtual meeting

[Jan Høydahl]

Thanks for taking the lead and pulling this off David. This is very positive 
for the community, it supplements the lists in a very nice way.

Jan Høydahl

> 23. mar. 2020 kl. 13:48 skrev David Smiley :
> 
> 
> I updated the cwiki page on the meeting notes after the meeting to reflect 
> what we talked about.  Sometimes it was just a couple sentences by myself.  
> Some topics are annotated as something we didn't get to / review.
> https://cwiki.apache.org/confluence/display/LUCENE/2020-03+Meeting+notes
> 
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley
> 
> 
>> On Fri, Mar 13, 2020 at 12:36 AM David Smiley  
>> wrote:
>> I've chosen Friday March 20th at 11am US eastern time, which is when 
>> everyone who responded to the Doodle poll said they could make it.  Closer 
>> to the event I'll share a Google Hangout URL on Slack #lucene-dev.  This 
>> gathering is virtual and so no coronavirus cancellation will happen ;-)
>> 
>> ~ David Smiley
>> Apache Lucene/Solr Search Developer
>> http://www.linkedin.com/in/davidwsmiley
>> 
>> 
>>> On Tue, Mar 10, 2020 at 5:27 PM David Smiley  
>>> wrote:
>>> Hello fellow committers,
>>> 
>>> I'd like to organize another virtual Lucene/Solr committer meeting this 
>>> month.  I created a meeting notes page in confluence here: 
>>> https://cwiki.apache.org/confluence/display/LUCENE/2020-03+Meeting+notes
>>> It has some topics I'd like to talk about and I'm hoping others might add 
>>> to the tentative agenda as well.  Maybe we'll keep it to an hour this time; 
>>> last time it was 95 minutes.
>>> 
>>> When exactly is this?:  Next week sometime.  I'm using a "Doodle poll" to 
>>> determine an optimal time slot.  For the link to the poll, go to the ASF 
>>> Slack, #lucene-dev channel, and you will see it.  You could also email me 
>>> directly for it.
>>> 
>>> For this virtual committer meeting and future ones:
>>> This is in the spirit of committer meetings co-located with conferences.  
>>> ASF policy says that no "decisions" can be made in such a venue.  We make 
>>> decisions on this dev list and indirectly via JIRA out in the open and with 
>>> the opportunity for anyone to comment.
>>> Who:  Committer-only or by invitation
>>> Video chat with option of audio dial-in.  This time I will use Google 
>>> Hangout.
>>> Recorded for those invited only.  I'll dispose of the recording a week 
>>> after.  The intention is for those who cannot be there due to a scheduling 
>>> conflict to see/hear what was said.  I have the ability to do this 
>>> recording via Salesforce's G-Suite subscription.
>>> Published notes:  I (or someone) will take written meeting notes that are 
>>> ultimately published for anyone to see (not restricted to those invited).  
>>> They will be transmitted to the dev list.
>>> 
>>> 
>>> ~ David Smiley
>>> Apache Lucene/Solr Search Developer
>>> http://www.linkedin.com/in/davidwsmiley

Re: 2020-03 Committer virtual meeting

[David Smiley]

I updated the cwiki page on the meeting notes after the meeting to reflect
what we talked about.  Sometimes it was just a couple sentences by myself.
Some topics are annotated as something we didn't get to / review.
https://cwiki.apache.org/confluence/display/LUCENE/2020-03+Meeting+notes

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Fri, Mar 13, 2020 at 12:36 AM David Smiley 
wrote:

> I've chosen Friday March 20th at 11am US eastern time, which is when
> everyone who responded to the Doodle poll said they could make it.  Closer
> to the event I'll share a Google Hangout URL on Slack #lucene-dev.  This
> gathering is virtual and so no coronavirus cancellation will happen ;-)
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley
>
>
> On Tue, Mar 10, 2020 at 5:27 PM David Smiley 
> wrote:
>
>> Hello fellow committers,
>>
>> I'd like to organize another virtual Lucene/Solr committer meeting this
>> month.  I created a meeting notes page in confluence here:
>> https://cwiki.apache.org/confluence/display/LUCENE/2020-03+Meeting+notes
>> It has some topics I'd like to talk about and I'm hoping others might add
>> to the tentative agenda as well.  Maybe we'll keep it to an hour this time;
>> last time it was 95 minutes.
>>
>> When exactly is this?:  Next week sometime. I'm using a "Doodle poll" to
>> determine an optimal time slot.  For the link to the poll, go to the ASF
>> Slack, #lucene-dev channel, and you will see it.  You could also email me
>> directly for it.
>>
>> For this virtual committer meeting and future ones:
>>
>>- This is in the spirit of committer meetings co-located with
>>conferences.  ASF policy says that no "decisions" can be made in such a
>>venue.  We make decisions on this dev list and indirectly via JIRA out in
>>the open and with the opportunity for anyone to comment.
>>- Who:  Committer-only or by invitation
>>- Video chat with option of audio dial-in.  This time I will use
>>Google Hangout.
>>- Recorded for those invited only.  I'll dispose of the recording a
>>week after.  The intention is for those who cannot be there due to a
>>scheduling conflict to see/hear what was said.  I have the ability to do
>>this recording via Salesforce's G-Suite subscription.
>>- Published notes:  I (or someone) will take written meeting notes
>>that are ultimately published for anyone to see (not restricted to those
>>invited).  They will be transmitted to the dev list.
>>
>>
>>
>> ~ David Smiley
>> Apache Lucene/Solr Search Developer
>> http://www.linkedin.com/in/davidwsmiley
>>
>

RE: svn commit: r1058194 - in /websites/production/lucene/content/core/8_5_0: ./ analyzers-common/ analyzers-common/org/ analyzers-common/org/apache/ analyzers-common/org/apache/lucene/ analyzers-comm

[Uwe Schindler]

I can confirm, it's uptodate already:
https://lucene.apache.org/core/8_5_0/index.html

That was some point which was not yet fully tested, if automatisms work!

Uwe

-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de

> -Original Message-
> From: romseyg...@apache.org 
> Sent: Monday, March 23, 2020 1:00 PM
> To: comm...@lucene.apache.org
> Subject: svn commit: r1058194 - in
> /websites/production/lucene/content/core/8_5_0: ./ analyzers-common/
> analyzers-common/org/ analyzers-common/org/apache/ analyzers-
> common/org/apache/lucene/ analyzers-common/org/apache/lucene/analysis/
> analyzers-common/org/apac...
> 
> Author: romseygeek
> Date: Mon Mar 23 11:59:10 2020
> New Revision: 1058194
> 
> Log:
> Add docs, changes and javadocs for Lucene 8.5.0
> 
> 
> [This commit notification would consist of 1498 parts,
> which exceeds the limit of 50 ones, so it was shortened to the summary.]


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

RE: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build # 5796 - Still Failing!

[Uwe Schindler]

I updated the Python installation on Policeman Jenkins Macos Slave. It no 
longer uses the OS default, I hope all works well.

Uwe

-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de

> -Original Message-
> From: Uwe Schindler 
> Sent: Monday, March 23, 2020 12:20 PM
> To: 'dev@lucene.apache.org' 
> Subject: RE: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build #
> 5796 - Still Failing!
> 
> For more info see:
> https://pyfound.blogspot.com/2017/01/time-to-upgrade-your-python-tls-
> v12.html
> 
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
> 
> > -Original Message-
> > From: Uwe Schindler 
> > Sent: Monday, March 23, 2020 11:53 AM
> > To: dev@lucene.apache.org
> > Subject: RE: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build
> #
> > 5796 - Still Failing!
> >
> > It looks like the python installed on MacOS installed by default can't 
> > handle
> TLS
> > 1.2. Policeman jenkins now requires a minimum version of TLS 1.2.
> >
> > I will disable the reproducer for now.
> >
> > Uwe
> >
> > -
> > Uwe Schindler
> > Achterdiek 19, D-28357 Bremen
> > https://www.thetaphi.de
> > eMail: u...@thetaphi.de
> >
> > > -Original Message-
> > > From: Policeman Jenkins Server 
> > > Sent: Monday, March 23, 2020 11:30 AM
> > > To: bui...@lucene.apache.org
> > > Subject: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build #
> > > 5796 - Still Failing!
> > >
> > > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/5796/
> > > Java: 64bit/jdk-13.0.2 -XX:-UseCompressedOops -XX:+UseSerialGC
> > >
> > > All tests passed
> > >
> > > Build Log:
> > > [...truncated 68436 lines...]
> > > [repro] Jenkins log URL: 
> > > https://jenkins.thetaphi.de/job/Lucene-Solr-master-
> > > MacOSX/5796/consoleText
> > >
> > > [...truncated 48 lines...]
> > > raise RuntimeError('ERROR: fetching %s : %s' % (url, e))
> > > RuntimeError: ERROR: fetching https://jenkins.thetaphi.de/job/Lucene-Solr-
> > > master-MacOSX/5796/consoleText :  > > error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol
> > > version>
> > > Build step 'Execute shell' marked build as failure
> > > Archiving artifacts
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> > > [WARNINGS] Skipping publisher since build result is FAILURE
> > > Recording test results
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> > > Email was triggered for: Failure - Any
> > > Sending email for trigger: Failure - Any
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> > > Setting
> > >
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > > _1.8.2
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

RE: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build # 5796 - Still Failing!

[Uwe Schindler]

For more info see:
https://pyfound.blogspot.com/2017/01/time-to-upgrade-your-python-tls-v12.html

-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de

> -Original Message-
> From: Uwe Schindler 
> Sent: Monday, March 23, 2020 11:53 AM
> To: dev@lucene.apache.org
> Subject: RE: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build #
> 5796 - Still Failing!
> 
> It looks like the python installed on MacOS installed by default can't handle 
> TLS
> 1.2. Policeman jenkins now requires a minimum version of TLS 1.2.
> 
> I will disable the reproducer for now.
> 
> Uwe
> 
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
> 
> > -Original Message-
> > From: Policeman Jenkins Server 
> > Sent: Monday, March 23, 2020 11:30 AM
> > To: bui...@lucene.apache.org
> > Subject: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build #
> > 5796 - Still Failing!
> >
> > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/5796/
> > Java: 64bit/jdk-13.0.2 -XX:-UseCompressedOops -XX:+UseSerialGC
> >
> > All tests passed
> >
> > Build Log:
> > [...truncated 68436 lines...]
> > [repro] Jenkins log URL: https://jenkins.thetaphi.de/job/Lucene-Solr-master-
> > MacOSX/5796/consoleText
> >
> > [...truncated 48 lines...]
> > raise RuntimeError('ERROR: fetching %s : %s' % (url, e))
> > RuntimeError: ERROR: fetching https://jenkins.thetaphi.de/job/Lucene-Solr-
> > master-MacOSX/5796/consoleText :  > error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol
> > version>
> > Build step 'Execute shell' marked build as failure
> > Archiving artifacts
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> > [WARNINGS] Skipping publisher since build result is FAILURE
> > Recording test results
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> > Email was triggered for: Failure - Any
> > Sending email for trigger: Failure - Any
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> > Setting
> >
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> > _1.8.2
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

RE: 8.5 release

[Uwe Schindler]

Hi,

 

the Javadocs are not in the repository with that magic file, they are in the 
“production” tree (only the website). The Javadocs are still at the same 
position:

 

https://svn.apache.org/repos/infra/websites/production/lucene/content

 

All instructions regarding extpaths.txt is obsolete, the new website is in git 
and there you only have to change one line in the config file to point to 
latest version:

 

See https://github.com/apache/lucene-site for instructions. I am available for 
chat on Slack.

 

Uwe

 

-

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de

eMail: u...@thetaphi.de

 

From: Alan Woodward  
Sent: Monday, March 23, 2020 11:52 AM
To: dev@lucene.apache.org
Subject: Re: 8.5 release

 

Hi all,

 

Just to say that the release is still happening, it’s just taking a bit longer 
than usual to get things sorted due to some external circumstances…

 

The release is now on the apache mirrors and maven central (we need to update 
the poll_mirrors script to correctly handle https, as lots of the mirrors no 
longer accept http).  I’m trying to update the website with the new java docs, 
but it looks as though this has all been changed since the last release, and 
the instructions on our release website no longer apply.  In particular, the 
svn repository where the java docs used to sit now has a single empty file 
called MOVED_TO_GIT - if anybody knows more about this, please chime in!

 

- A





On 19 Mar 2020, at 15:06, Alan Woodward mailto:romseyg...@gmail.com> > wrote:

 

I’ll check on the Lucene notes.  Thanks Cassandra!





On 19 Mar 2020, at 14:06, Cassandra Targett mailto:casstarg...@gmail.com> > wrote:

 

I’ll look to add the release instructions soon. There is a page in the Ref 
Guide that describes how to do it (it’s basically the same as javadocs, just a 
different ant/gradle target). 

 

I also created a new top-level page in Solr’s Confluence for Release Notes: 
https://cwiki.apache.org/confluence/display/SOLR/Release+Notes. I only moved 
8.x and a couple 7.x notes there for now (it’s a bit tedious to move them, but 
anyone would be welcome to keep going) so we can use that spot to put them from 
now on. I didn’t check, though, if Lucene’s Confluence has the same problem of 
notes being buried? Sorry to half-complete the task, I was looking for Solr's 
notes and got annoyed I can never find them quickly.

 

Cassandra

On Mar 17, 2020, 5:50 AM -0500, Alan Woodward mailto:romseyg...@gmail.com> >, wrote:



If you add the release instructions to the ReleaseTodo page on cwiki then the 
RM should be able to follow them.  I can look into adding them to the release 
wizard as well.





On 16 Mar 2020, at 15:15, Cassandra Targett mailto:casstarg...@gmail.com> > wrote:

 

What do we need to do to get pushing the Ref Guide up as part of the RM 
process? It’s super simple now, but I’m not sure what needs to change to make 
it happen regularly as part of release.

 

Cassandra

On Mar 16, 2020, 3:48 AM -0500, Alan Woodward mailto:romseyg...@gmail.com> >, wrote:



Let’s keep both pages as Draft for now - one advantage of Cwiki over moin is 
that we can delay publishing our release notes until the release has actually 
happened.





On 16 Mar 2020, at 08:20, Mikhail Khludnev mailto:m...@apache.org> > wrote:

 


Alan, I've added a point. Should I click [Publish]?

 

On Fri, Mar 13, 2020 at 5:31 PM Alan Woodward mailto:romseyg...@gmail.com> > wrote:

That’s the one, thank you Jan!  I’ve cloned it and made minimal changes to 
update it to 8.5, it still needs the release highlights adding in though.  
Draft page is available here: 

https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=148641910 

 
=8a43c9fb-6845-413a-b6cd-876a6647bb32=shareui=1584107316180

 

We should definitely make a top-level page for these, they currently sit under 
‘Old Wiki’ which doesn’t seem right at all.





On 13 Mar 2020, at 11:20, Jan Høydahl mailto:jan@cominvent.com> > wrote:

 

Perhaps this is the one you are looking for? 
https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote84 

 

We should probably make a top-level page «Release Notes» under which we can 
attach future release notes.

 

Jan





12. mar. 2020 kl. 17:24 skrev Alan Woodward mailto:romseyg...@gmail.com> >:

 

While I wait for the smoke tester to finish, I’ve been working on release 
notes.  The ReleaseTodo still refers to the old wiki, and release notes are on 
CWiki now, so I’m flying slightly blind.  Looking at what was done for the 
previous release, I’ve created a draft note for lucene which can be inspected 
and edited here: 

 

https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=148641343 

RE: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build # 5796 - Still Failing!

[Uwe Schindler]

It looks like the python installed on MacOS installed by default can't handle 
TLS 1.2. Policeman jenkins now requires a minimum version of TLS 1.2.

I will disable the reproducer for now.

Uwe

-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de

> -Original Message-
> From: Policeman Jenkins Server 
> Sent: Monday, March 23, 2020 11:30 AM
> To: bui...@lucene.apache.org
> Subject: [JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk-13.0.2) - Build #
> 5796 - Still Failing!
> 
> Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/5796/
> Java: 64bit/jdk-13.0.2 -XX:-UseCompressedOops -XX:+UseSerialGC
> 
> All tests passed
> 
> Build Log:
> [...truncated 68436 lines...]
> [repro] Jenkins log URL: https://jenkins.thetaphi.de/job/Lucene-Solr-master-
> MacOSX/5796/consoleText
> 
> [...truncated 48 lines...]
> raise RuntimeError('ERROR: fetching %s : %s' % (url, e))
> RuntimeError: ERROR: fetching https://jenkins.thetaphi.de/job/Lucene-Solr-
> master-MacOSX/5796/consoleText :  error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol
> version>
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2
> [WARNINGS] Skipping publisher since build result is FAILURE
> Recording test results
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2
> Setting
> ANT_1_8_2_HOME=/Users/jenkins/tools/hudson.tasks.Ant_AntInstallation/ANT
> _1.8.2


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 8.5 release

[Alan Woodward]

Hi all,

Just to say that the release is still happening, it’s just taking a bit longer 
than usual to get things sorted due to some external circumstances…

The release is now on the apache mirrors and maven central (we need to update 
the poll_mirrors script to correctly handle https, as lots of the mirrors no 
longer accept http).  I’m trying to update the website with the new java docs, 
but it looks as though this has all been changed since the last release, and 
the instructions on our release website no longer apply.  In particular, the 
svn repository where the java docs used to sit now has a single empty file 
called MOVED_TO_GIT - if anybody knows more about this, please chime in!

- A

> On 19 Mar 2020, at 15:06, Alan Woodward  wrote:
> 
> I’ll check on the Lucene notes.  Thanks Cassandra!
> 
>> On 19 Mar 2020, at 14:06, Cassandra Targett > > wrote:
>> 
>> I’ll look to add the release instructions soon. There is a page in the Ref 
>> Guide that describes how to do it (it’s basically the same as javadocs, just 
>> a different ant/gradle target).
>> 
>> I also created a new top-level page in Solr’s Confluence for Release Notes: 
>> https://cwiki.apache.org/confluence/display/SOLR/Release+Notes 
>> . I only 
>> moved 8.x and a couple 7.x notes there for now (it’s a bit tedious to move 
>> them, but anyone would be welcome to keep going) so we can use that spot to 
>> put them from now on. I didn’t check, though, if Lucene’s Confluence has the 
>> same problem of notes being buried? Sorry to half-complete the task, I was 
>> looking for Solr's notes and got annoyed I can never find them quickly.
>> 
>> Cassandra
>> On Mar 17, 2020, 5:50 AM -0500, Alan Woodward > >, wrote:
>>> If you add the release instructions to the ReleaseTodo page on cwiki then 
>>> the RM should be able to follow them.  I can look into adding them to the 
>>> release wizard as well.
>>> 
 On 16 Mar 2020, at 15:15, Cassandra Targett >>> > wrote:
 
 What do we need to do to get pushing the Ref Guide up as part of the RM 
 process? It’s super simple now, but I’m not sure what needs to change to 
 make it happen regularly as part of release.
 
 Cassandra
 On Mar 16, 2020, 3:48 AM -0500, Alan Woodward >>> >, wrote:
> Let’s keep both pages as Draft for now - one advantage of Cwiki over moin 
> is that we can delay publishing our release notes until the release has 
> actually happened.
> 
>> On 16 Mar 2020, at 08:20, Mikhail Khludnev > > wrote:
>> 
>> 
>> Alan, I've added a point. Should I click [Publish]?
>> 
>> On Fri, Mar 13, 2020 at 5:31 PM Alan Woodward > > wrote:
>> That’s the one, thank you Jan!  I’ve cloned it and made minimal changes 
>> to update it to 8.5, it still needs the release highlights adding in 
>> though.  Draft page is available here:
>> https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=148641910=8a43c9fb-6845-413a-b6cd-876a6647bb32=shareui=1584107316180
>>  
>> 
>> 
>> We should definitely make a top-level page for these, they currently sit 
>> under ‘Old Wiki’ which doesn’t seem right at all.
>> 
>>> On 13 Mar 2020, at 11:20, Jan Høydahl >> > wrote:
>>> 
>>> Perhaps this is the one you are looking for? 
>>> https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote84 
>>> 
>>> 
>>> We should probably make a top-level page «Release Notes» under which we 
>>> can attach future release notes.
>>> 
>>> Jan
>>> 
 12. mar. 2020 kl. 17:24 skrev Alan Woodward >>> >:
 
 While I wait for the smoke tester to finish, I’ve been working on 
 release notes.  The ReleaseTodo still refers to the old wiki, and 
 release notes are on CWiki now, so I’m flying slightly blind.  Looking 
 at what was done for the previous release, I’ve created a draft note 
 for lucene which can be inspected and edited here:
 
 https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=148641343=d4d3acb9-0dd6-4d40-903c-b16f2bb68415=shareui=1584025014586
  
 
 
 For Solr, the 8.4 release note on CWiki points to a section on 
 https://lucene.apache.org/solr/news.html