This is an automated email from the ASF dual-hosted git repository. janhoy pushed a commit to branch Fix-lucene.apache.org-links in repository https://gitbox.apache.org/repos/asf/solr.git
commit 94cbb80fa679d3753127f8c1915be0751f24a852 Author: Jan Høydahl <[email protected]> AuthorDate: Tue Dec 21 18:20:07 2021 +0100 More links --- dev-docs/pmc-chair.adoc | 6 +++--- dev-tools/scripts/releaseWizard.yaml | 14 +++++++------- solr/README.md | 2 +- solr/core/src/java/org/apache/solr/core/SolrCore.java | 2 +- .../sample_techproducts_configs/conf/xslt/example_atom.xsl | 2 +- .../src/java/org/apache/solr/SolrTestCaseJ4.java | 2 +- solr/test-framework/src/resources/create-keystores.sh | 4 ++-- 7 files changed, 16 insertions(+), 16 deletions(-) diff --git a/dev-docs/pmc-chair.adoc b/dev-docs/pmc-chair.adoc index f0b0393..821a4c4 100644 --- a/dev-docs/pmc-chair.adoc +++ b/dev-docs/pmc-chair.adoc @@ -81,9 +81,9 @@ The standard process for handling vulnerability reports is defined at https://ww *All vulnerability reports must be handled with discretion and should not be discussed outside the Apache Security team and the PMC.* The reason for this is to prevent the vulnerability from being exploited before we have a chance to come up with proper mitigation steps and/or bug fixes. === How Vulnerabilities are Reported -The mailing list [email protected] has been set up to handle vulnerability reports. This list includes the Apache Security team, so they do not need to be cc'd on mails to that list. PMC members are unfortunately not automatically subscribed to this list, they must subscribe themselves. +The mailing list [email protected] has been set up to handle vulnerability reports. This list includes the Apache Security team, so they do not need to be cc'd on mails to that list. PMC members are unfortunately not automatically subscribed to this list, they must subscribe themselves. -The Apache Security team should be kept in the loop regarding how we decide to handle any vulnerability report. They are not cc'd on mails to [email protected], so if discussion happens there, [email protected] should be copied where appropriate. +The Apache Security team should be kept in the loop regarding how we decide to handle any vulnerability report. They are not cc'd on mails to [email protected], so if discussion happens there, [email protected] should be copied where appropriate. Vulnerabilities may also be reported via Jira. When this happens, the Security Level field in the issue must be set to "Private", which means it can only be viewed by members of the PMC. @@ -138,7 +138,7 @@ Private PMC files: https://svn.apache.org/repos/private/pmc/lucene/ The Lucene PMC traditionally rotates the Chair once a year. When it's time to change Chairs, think of a member of the PMC to replace you and ask if they will be willing to serve a term as Chair. -If they agree, you can start a VOTE thread in [email protected] nominating your successor. +If they agree, you can start a VOTE thread in [email protected] nominating your successor. Assuming the vote passes, you can send a resolution to the Board for their approval to change the Chair. Include the vote thread in the resolution. You do not need to wait until the usual quarterly report is due to change the Chair. diff --git a/dev-tools/scripts/releaseWizard.yaml b/dev-tools/scripts/releaseWizard.yaml index 459aeb3..cde6293 100644 --- a/dev-tools/scripts/releaseWizard.yaml +++ b/dev-tools/scripts/releaseWizard.yaml @@ -64,7 +64,7 @@ templates: (( template=vote_logic )) .Mail template {% if passed %}successful{% else %}failed{% endif %} vote ---- - To: [email protected] + To: [email protected] Subject: [{% if passed %}RESULT{% else %}FAILED{% endif %}] [VOTE] Release Lucene/Solr {{ release_version }} RC{{ rc_number }} It's been >72h since the vote was initiated and the result is: @@ -137,7 +137,7 @@ templates: .Mail template ---- - To: [email protected], [email protected], [email protected] + To: [email protected], [email protected] Subject: [ANNOUNCE] Apache Lucene {{ release_version }} released (( template=announce_lucene_mail_body )) @@ -171,7 +171,7 @@ templates: .Mail template ---- - To: [email protected], [email protected], [email protected] + To: [email protected], [email protected] Subject: [ANNOUNCE] Apache Solr {{ release_version }} released (( template=announce_solr_mail_body )) @@ -548,7 +548,7 @@ groups: .Mail template ---- - To: [email protected] + To: [email protected] Subject: New branch and feature freeze for Lucene/Solr {{ release_version }} NOTICE: @@ -588,7 +588,7 @@ groups: .Mail template ---- - To: [email protected] + To: [email protected] Subject: Bugfix release Lucene/Solr {{ release_version }} NOTICE: @@ -799,7 +799,7 @@ groups: .Mail template ---- - To: [email protected] + To: [email protected] Subject: [VOTE] Release Lucene/Solr {{ release_version }} RC{{ rc_number }} Please vote for release candidate {{ rc_number }} for Lucene/Solr {{ release_version }} @@ -1232,7 +1232,7 @@ groups: - stage_website description: | Push the website changes to 'production' branch. This will build and publish the live site on - https://lucene.apache.org + https://solr.apache.org commands: !Commands root_folder: '{{ git_website_folder }}' commands: diff --git a/solr/README.md b/solr/README.md index d2dc8ea..e675ada 100644 --- a/solr/README.md +++ b/solr/README.md @@ -23,7 +23,7 @@ from the Apache Lucene project. For a complete description of the Solr project, team composition, source code repositories, and other details, please see the Solr web site at -https://lucene.apache.org/solr +https://solr.apache.org/solr Getting Started diff --git a/solr/core/src/java/org/apache/solr/core/SolrCore.java b/solr/core/src/java/org/apache/solr/core/SolrCore.java index 4705d5f..5d8281a 100644 --- a/solr/core/src/java/org/apache/solr/core/SolrCore.java +++ b/solr/core/src/java/org/apache/solr/core/SolrCore.java @@ -1584,7 +1584,7 @@ public final class SolrCore implements SolrInfoBean, Closeable { int count = refCount.decrementAndGet(); if (count > 0) return; // close is called often, and only actually closes if nothing is using it. if (count < 0) { - log.error("Too many close [count:{}] on {}. Please report this exception to [email protected]", count, this); + log.error("Too many close [count:{}] on {}. Please report this exception to [email protected]", count, this); assert false : "Too many closes on SolrCore"; return; } diff --git a/solr/server/solr/configsets/sample_techproducts_configs/conf/xslt/example_atom.xsl b/solr/server/solr/configsets/sample_techproducts_configs/conf/xslt/example_atom.xsl index b6c2315..8c36bac 100644 --- a/solr/server/solr/configsets/sample_techproducts_configs/conf/xslt/example_atom.xsl +++ b/solr/server/solr/configsets/sample_techproducts_configs/conf/xslt/example_atom.xsl @@ -40,7 +40,7 @@ </subtitle> <author> <name>Apache Solr</name> - <email>[email protected]</email> + <email>[email protected]</email> </author> <link rel="self" type="application/atom+xml" href="http://localhost:8983/solr/q={$query}&wt=xslt&tr=atom.xsl"/> diff --git a/solr/test-framework/src/java/org/apache/solr/SolrTestCaseJ4.java b/solr/test-framework/src/java/org/apache/solr/SolrTestCaseJ4.java index 9530b95..5a1bb26 100644 --- a/solr/test-framework/src/java/org/apache/solr/SolrTestCaseJ4.java +++ b/solr/test-framework/src/java/org/apache/solr/SolrTestCaseJ4.java @@ -2913,7 +2913,7 @@ public abstract class SolrTestCaseJ4 extends SolrTestCase { assertFalse("SecureRandom algorithm '" + algorithm + "' is in use by your JVM, " + "which is a potentially blocking algorithm on some environments. " + - "Please report the details of this failure (and your JVM vendor/version) to [email protected]. " + + "Please report the details of this failure (and your JVM vendor/version) to [email protected]. " + "You can try to run your tests with -D"+EGD+"="+URANDOM+" or bypass this check using " + "-Dtest.solr.allowed.securerandom="+ algorithm +" as a JVM option when running tests.", // be permissive in our checks and deny only algorithms diff --git a/solr/test-framework/src/resources/create-keystores.sh b/solr/test-framework/src/resources/create-keystores.sh index 0b43f28..0dc3d86 100755 --- a/solr/test-framework/src/resources/create-keystores.sh +++ b/solr/test-framework/src/resources/create-keystores.sh @@ -28,10 +28,10 @@ echo "### remove old keystores" rm -f SSLTestConfig.testing.keystore SSLTestConfig.hostname-and-ip-missmatch.keystore echo "### create 'localhost' keystore and keys" -keytool -keystore SSLTestConfig.testing.keystore -storepass "secret" -alias solrtest -keypass "secret" -genkey -keyalg RSA -dname "cn=localhost, ou=SolrTest, o=lucene.apache.org, c=US" -ext "san=dns:localhost,ip:127.0.0.1" -validity 999999 +keytool -keystore SSLTestConfig.testing.keystore -storepass "secret" -alias solrtest -keypass "secret" -genkey -keyalg RSA -dname "cn=localhost, ou=SolrTest, o=solr.apache.org, c=US" -ext "san=dns:localhost,ip:127.0.0.1" -validity 999999 # See https://tools.ietf.org/html/rfc5737 echo "### create 'Bogus Host' keystore and keys" -keytool -keystore SSLTestConfig.hostname-and-ip-missmatch.keystore -storepass "secret" -alias solrtest -keypass "secret" -genkey -keyalg RSA -dname "cn=bogus.hostname.tld, ou=SolrTest, o=lucene.apache.org, c=US" -ext "san=dns:bogus.hostname.tld,ip:192.0.2.0" -validity 999999 +keytool -keystore SSLTestConfig.hostname-and-ip-missmatch.keystore -storepass "secret" -alias solrtest -keypass "secret" -genkey -keyalg RSA -dname "cn=bogus.hostname.tld, ou=SolrTest, o=solr.apache.org, c=US" -ext "san=dns:bogus.hostname.tld,ip:192.0.2.0" -validity 999999
