This repository has been archived by the owner on Apr 2, 2023. It is now read-only.
Release update #235
Merged
Release update #235
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er used. Fixes some style issues on committers guide.
|
@lenhattan86 can you follow the instructions here and see if they work? |
|
sure. let me try it out
…On Thu, Jun 17, 2021 at 12:36 PM Renán I. Del Valle < ***@***.***> wrote:
@lenhattan86 <https://github.com/lenhattan86> can you follow the
instructions here and see if they work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#235 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCJ5RZFTUNCUSJCMOVPLQTTTJFDPANCNFSM464JWMKA>
.
|
lenhattan86
reviewed
Jun 17, 2021
| 1. Ensure that all issues resolved for this release candidate are tagged with the correct Fix | ||
| Version in JIRA, the changelog script will use this to generate the CHANGELOG in step #2. | ||
| To assign the fix version: | ||
| 1. Ensure that all merged pull requests for this release candidate are tagged with the correct version, |
There was a problem hiding this comment.
It is not clear for me how to verify the tagged versions. For example, if we have a PR merged on top of 0.24.1. should it be tagged with 0.24.1?
If it is not tagged correctly. How do we fix it?
lenhattan86
reviewed
Jun 17, 2021
| * Query all issues resolved after that release date: `project = AURORA AND status in (resolved, Closed) and fixVersion is empty and resolutiondate >= "YYYY/MM/DD"` | ||
| * In the upper right corner of the query result, select Tools > Bulk Edit. | ||
| * Select all issues > edit issue > set 'Change Fix Version/s' to the release version. | ||
| * Make sure to uncheck 'Send mail for this update' at the bottom. | ||
|
|
||
| 2. Prepare RELEASE-NOTES.md for the release. This just boils down to removing the "(Not yet |
There was a problem hiding this comment.
line 51 should be 3. etc
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Updating release instructions to reflect the project reboot in Github.
Testing Done:
Released Aurora 0.24.1 with instructions