[
https://issues.apache.org/jira/browse/BEAM-6445?focusedWorklogId=187036&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-187036
]
ASF GitHub Bot logged work on BEAM-6445:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jan/19 21:14
Start Date: 18/Jan/19 21:14
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #7529:
[BEAM-6445]: Release Guide changes for release process improvement
URL: https://github.com/apache/beam/pull/7529#discussion_r249187128
##########
File path: website/src/contribute/release-guide.md
##########
@@ -428,6 +422,44 @@ Javadoc to the Javadoc for other modules that Beam
depends on.
the version number has changed, download a new version of the corresponding
`<module>-docs/package-list` file.
+### Triage release-blocking issues in JIRA
+
+There could be outstanding release-blocking issues, which should be triaged
before proceeding to build a release candidate. We track them by assigning a
specific `Fix version` field even before the issue resolved.
+
+The list of release-blocking issues is available at the [version status
page](https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel).
Triage each unresolved issue with one of the following resolutions:
+
+For all JIRA issues:
+
+* If the issue has been resolved and JIRA was not updated, resolve it
accordingly.
+
+For JIRA issues with type "Bug" or labeled "flaky":
+
+* If the issue is a known continuously failing test, it is not acceptable to
defer this until the next release. Please work with the Beam community to
resolve the issue.
+* If the issue is a known flaky test, make an attempt to fix the issue.
However, if the issue may take too long to fix (to the discretion of the
release manager):
Review comment:
This might not be super clear - I think the release manager should make an
attempt to _get the test fixed_ but often by delegating / asking someone else,
just like the next bullet.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 187036)
Time Spent: 2h 40m (was: 2.5h)
> Improve Release Process
> -----------------------
>
> Key: BEAM-6445
> URL: https://issues.apache.org/jira/browse/BEAM-6445
> Project: Beam
> Issue Type: Improvement
> Components: project-management
> Reporter: Sam Rohde
> Assignee: Sam Rohde
> Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> This JIRA tracks the improvement of the Beam release process as [discussed in
> the dev
> list|https://lists.apache.org/thread.html/d52ffbfca21eee953a230100520bd56d947a359c0029d5c291b736a7@%3Cdev.beam.apache.org%3E].
> In summary, this change will hopefully increase the greenness of the build
> by: increasing coverage, adding pre and post commits to release validation,
> and adding a regular cadence to look at flaky and backlogged tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
