mirror of https://github.com/apache/lucene.git
Replace JIRA release instructions with GitHub. (#11968)
This commit is contained in:
Adrien Grand
GitHub
parent
e9dc4f9188
commit
f5ea0412eb
|
|
@ -551,12 +551,12 @@ groups:
|
|||
* Before committing to the branch, reply to this thread and argue
|
||||
why the fix needs backporting and how long it will take.
|
||||
* All issues accepted for backporting should be marked with {{ release_version }}
|
||||
in JIRA, and issues that should delay the release must be marked as Blocker
|
||||
in GitHub, and issues that should delay the release must be marked as Blocker
|
||||
* 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.
|
||||
* Only Jira issues with Fix version {{ release_version }} and priority "Blocker" will delay
|
||||
a release candidate build.
|
||||
* Only GitHub issues or pull requests with milestone {{ release_version }} and
|
||||
priority "Blocker" will delay a release candidate build.
|
||||
----
|
||||
types:
|
||||
- bugfix
|
||||
|
|
@ -571,14 +571,14 @@ groups:
|
|||
Ask on dev@ for input. Ideally the timing of this request mostly coincides with the
|
||||
release branch creation. It's a good idea to remind the devs of this later in the release too.
|
||||
|
||||
NOTE: Do not add every single JIRA issue, but distill the Release note into important changes!
|
||||
NOTE: Do not add every single GitHub PR, but distill the Release note into important changes!
|
||||
links:
|
||||
- https://cwiki.apache.org/confluence/display/LUCENE/Release+Notes
|
||||
- !Todo
|
||||
id: new_jira_versions
|
||||
title: Add a new version in JIRA for the next release
|
||||
id: new_github_versions
|
||||
title: Add a new version in GitHub for the next release
|
||||
description: |-
|
||||
Go to the JIRA "Manage Versions" Administration pages and add the new version:
|
||||
Go to the GitHub milestones and add the new version:
|
||||
|
||||
{% if release_type == 'major' -%}
|
||||
. Change name of version `main ({{ release_version_major }}.0)` into `{{ release_version_major }}.0`
|
||||
|
|
@ -588,13 +588,13 @@ groups:
|
|||
- major
|
||||
- minor
|
||||
links:
|
||||
- https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions
|
||||
- https://github.com/apache/lucene/milestones
|
||||
- !TodoGroup
|
||||
id: artifacts
|
||||
title: Build the release artifacts
|
||||
description: |-
|
||||
If after the last day of the feature freeze phase no blocking issues are
|
||||
in JIRA with "Fix Version" {{ release_version }}, then it's time to build the
|
||||
in GitHub with milestone {{ release_version }}, then it's time to build the
|
||||
release artifacts, run the smoke tester and stage the RC in svn
|
||||
depends:
|
||||
- test
|
||||
|
|
@ -1344,8 +1344,8 @@ groups:
|
|||
CHANGES.txt files, removing any duplicate entries, but only from sections for as-yet
|
||||
unreleased versions; leave intact duplicate entries for already-released versions.
|
||||
|
||||
There is a script to generate a regex that will match JIRAs fixed in a release:
|
||||
`releasedJirasRegex.py`. The following examples will print regexes matching all JIRAs
|
||||
There is a script to generate a regex that will match issues fixed in a release:
|
||||
`releasedJirasRegex.py`. The following examples will print regexes matching all issues
|
||||
fixed in {{ release_version }}, which can then be used to find duplicates in unreleased
|
||||
version sections of the corresponding CHANGES.txt files.
|
||||
commands: !Commands
|
||||
|
|
@ -1517,55 +1517,32 @@ groups:
|
|||
because there was no released Lucene version to test against.
|
||||
{{ set_java_home(release_version) }}
|
||||
- !Todo
|
||||
id: jira_release
|
||||
title: Mark version as released in JIRA
|
||||
id: github_release
|
||||
title: Mark version as released in GitHub
|
||||
description: |-
|
||||
Go to the JIRA "Manage Versions" Administration pages.
|
||||
|
||||
. Next to version {{ release_version }}, click the gear pop-up menu icon and choose "Release"
|
||||
. Fill in the release date ({{ release_date | formatdate }})
|
||||
. It will give the option of transitioning issues marked fix-for the released version to the
|
||||
next version, but do not do this as it will send an email for each issue :)
|
||||
Go to https://github.com/apache/lucene/milestones.
|
||||
. Click "Close" on the version you just released.
|
||||
links:
|
||||
- https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions
|
||||
- https://github.com/apache/lucene/milestones
|
||||
- !Todo
|
||||
id: jira_close_resolved
|
||||
title: Close all issues resolved in the release
|
||||
id: github_change_unresolved
|
||||
title: Remove milestone for unresolved
|
||||
description: |-
|
||||
Go to JIRA search to find all issues that were fixed in the release
|
||||
you just made, whose Status is Resolved.
|
||||
Go to GitHub to update all open issues assigned to milestone _{{ release_version }}_.
|
||||
|
||||
. Go to https://issues.apache.org/jira/issues/?jql=project+in+(LUCENE)+AND+status=Resolved+AND+fixVersion={{ release_version }}
|
||||
. Do a bulk change (Under Tools... menu) to close all of these issues. This is a workflow transition task
|
||||
. In the 'Comment' box type `Closing after the {{ release_version }} release`
|
||||
. *Uncheck* the box that says `Send mail for this update`
|
||||
. Open https://github.com/apache/lucene/milestones/{{ release_version }}
|
||||
. Remove the milestone from all issues and pull requests that are still open.
|
||||
links:
|
||||
- https://issues.apache.org/jira/issues/?jql=project+in+(LUCENE)+AND+status=Resolved+AND+fixVersion={{ release_version }}
|
||||
- https://github.com/apache/lucene/milestones/{{ release_version }}
|
||||
- !Todo
|
||||
id: jira_change_unresolved
|
||||
title: Remove fixVersion for unresolved
|
||||
id: new_github_versions_bugfix
|
||||
title: Add a new milestone in GitHub for the next release
|
||||
description: |-
|
||||
Do another JIRA search to find all issues with Resolution=_Unresolved_ and fixVersion=_{{ release_version }}_.
|
||||
|
||||
. Open https://issues.apache.org/jira/issues/?jql=project+=+LUCENE+AND+resolution=Unresolved+AND+fixVersion={{ release_version }}
|
||||
. In the `Tools` menu, start a bulk change - operation="Edit issues"
|
||||
. Identify issues that *are included* in the release, but are unresolved e.g. due to being REOPENED. These shall *not* be bulk changed!
|
||||
. Check the box next to `Change Fix Version/s` and in the dropdown `Find and remove these`, selecting v {{ release_version }}
|
||||
. On the bottom of the form, uncheck the box that says `Send mail for this update`
|
||||
. Click `Next`, review the changes and click `Confirm`
|
||||
links:
|
||||
- https://issues.apache.org/jira/issues/?jql=project+=+LUCENE+AND+resolution=Unresolved+AND+fixVersion={{ release_version }}
|
||||
- !Todo
|
||||
id: new_jira_versions_bugfix
|
||||
title: Add a new version in JIRA for the next release
|
||||
description: |-
|
||||
Go to the JIRA "Manage Versions" Administration pages and add the new version:
|
||||
|
||||
. Create a new (unreleased) version `{{ get_next_version }}`
|
||||
Go to GitHub milestones and add the new version {{ get_next_version }}`.
|
||||
types:
|
||||
- bugfix
|
||||
links:
|
||||
- https://issues.apache.org/jira/plugins/servlet/project-config/LUCENE/versions
|
||||
- https://github.com/apache/lucene/milestones
|
||||
- !Todo
|
||||
id: stop_promoting_old
|
||||
title: Stop promoting old releases
|
||||
|
|
|
|||
Loading…
Reference in New Issue