Apache Lucene open-source search software
update DOAP and releaseWizard to reflect migration to github (#11747)
Michael Sokolovaccc3bdcfabe
diff --git a/dev-tools/doap/lucene.rdf b/dev-tools/doap/lucene.rdfindex bb970c25687..1eb94366ac4 100644--- a/dev-tools/doap/lucene.rdf+++ b/dev-tools/doap/lucene.rdf@@ -37,7 +37,7 @@<shortdesc>Apache Lucene is a high-performance, full-featured text search engine library</shortdesc><description>Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform.</description>- <bug-database rdf:resource="http://issues.apache.org/jira/browse/LUCENE" />+ <bug-database rdf:resource="https://github.com/apache/lucene/issues" /><mailing-list rdf:resource="http://lucene.apache.org/core/discussion.html" /><download-page rdf:resource="http://lucene.apache.org/core/downloads.html" /><programming-language>Java</programming-language>@@ -55,7 +55,7 @@<repository><GitRepository>- <location rdf:resource="https://git-wip-us.apache.org/repos/asf/lucene-solr.git"/>+ <location rdf:resource="https://git-wip-us.apache.org/repos/asf/lucene.git"/></GitRepository></repository>diff --git a/dev-tools/scripts/releaseWizard.py b/dev-tools/scripts/releaseWizard.pyindex 53052705896..b6a4c3df519 100755--- a/dev-tools/scripts/releaseWizard.py+++ b/dev-tools/scripts/releaseWizard.py@@ -1912,8 +1912,8 @@ today = datetime.utcnow().date()sundays = {(today + timedelta(days=x)): 'Sunday' for x in range(10) if (today + timedelta(days=x)).weekday() == 6}y = datetime.utcnow().yearyears = [y, y+1]-non_working = holidays.CA(years=years) + holidays.US(years=years) + holidays.England(years=years) \- + holidays.DE(years=years) + holidays.NO(years=years) + holidays.IND(years=years) + holidays.RU(years=years)+non_working = holidays.CA(years=years) + holidays.US(years=years) + holidays.UK(years=years) \+ + holidays.DE(years=years) + holidays.NO(years=years) + holidays.IN(years=years) + holidays.RU(years=years)def vote_close_72h_date():diff --git a/dev-tools/scripts/releaseWizard.yaml b/dev-tools/scripts/releaseWizard.yamlindex 6a95659eaf2..bc9764e3041 100644--- a/dev-tools/scripts/releaseWizard.yaml+++ b/dev-tools/scripts/releaseWizard.yaml@@ -249,8 +249,8 @@ groups:The ID is the last 8 bytes of your key fingerprint, e.g. 0D8D0B93.* Make sure your gpg key is 4096 bits key or larger- * Upload your key to the MIT key server, pgp.mit.edu- * Put you GPG key's fingerprint in the `OpenPGP Public Key Primary Fingerprint`+ * Upload your key to a key server: pgp.mit.edu or keys.openpgp.org+ * Put your GPG key's fingerprint in the `OpenPGP Public Key Primary Fingerprint`field in your id.apache.org profile* The tests will complain if your GPG key has not been signed by another Lucenecommitter. This makes you a part of the GPG "web of trust" (WoT). Ask a committer@@ -262,24 +262,15 @@ groups:- http://www.apache.org/dev/openpgp.html#apache-wot- https://id.apache.org- https://dist.apache.org/repos/dist/release/lucene/KEYS- - !Todo- id: jira_permissions- title: Obtain the neccessary permissions for Apache Jira- description: |-- If you are not a PMC member and this is your first time as RM, please ask to be granted extra permissions in Jira in order to complete all steps of the release.-- If you are a PMC member, you will already have the necessary permissions.- links:- - https://issues.apache.org/jira/projects/LUCENE- !TodoGroupid: preparationtitle: Prepare for the releasedescription: Work with the community to decide when the release will happen and what work must be completed before it can happentodos:- !Todo- id: decide_jira_issues- title: Select JIRA issues to be included- description: Set the appropriate "Fix Version" in JIRA for the issues that should be included in the release.+ id: decide_github_issues+ title: Select issues to be included+ description: Set the appropriate "Milestone" in Github for the issues that should be included in the release.- !Todoid: fix_build_failurestitle: Look into common build failures@@ -503,8 +494,8 @@ groups:* No new features may be committed to the branch.* Documentation patches, build patches and serious bug fixes may becommitted 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+ want to commit as pull requests first to give others the chance to review+ and possibly vote against them. Keep in mind that it is ourmain intention to keep the branch as stable as possible.* All patches that are intended for the branch should first be committedto the unstable branch, merged into the stable branch, and then into@@ -514,8 +505,8 @@ groups:while the branch feature freeze is in effect, think twice: can't theaddition wait a couple more days? Merges of bug fixes into the branchmay become more difficult.- * Only Jira issues with Fix version {{ release_version_major }}.{{ release_version_minor }} and priority "Blocker" will delay- a release candidate build.+ * Only Github issues with Milestone {{ release_version_major }}.{{ release_version_minor }}+ and priority "Blocker" will delay a release candidate build.----types:- major