[BEAM-1362] update release guide post 0.6.0 release#183
[BEAM-1362] update release guide post 0.6.0 release#183aaltay wants to merge 3 commits intoapache:asf-sitefrom
Conversation
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
LGTM |
|
retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id abe87e9 with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id ac0624a with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
aaltay
changed the title
|
@davorbonaci Do you have comments on this one? |
|
I'll have some comments, but I'll take a look on Monday if possible ;-) |
|
@davorbonaci Can I proceed with this one? |
davorbonaci
left a comment
davorbonaci
left a comment
There was a problem hiding this comment.
LGTM. Left only a few stylistic comments ;-)
src/contribute/release-guide.md
Outdated
| Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`. | ||
|
|
||
| Now, add your Apache GPG key to the Beam’s `KEYS` file both in [`dev`](https://dist.apache.org/repos/dist/dev/beam/KEYS) and [`release`](https://dist.apache.org/repos/dist/release/beam/KEYS) repositories at `dist.apache.org`. Follow the instructions listed at the top of these files. | ||
| Now, add your Apache GPG key to the Beam’s `KEYS` file both in [`dev`](https://dist.apache.org/repos/dist/dev/beam/KEYS) and [`release`](https://dist.apache.org/repos/dist/release/beam/KEYS) repositories at `dist.apache.org`. Follow the instructions listed at the top of these files. (Note: Not all committers have write access to the [`release`](https://dist.apache.org/repos/dist/release/beam/KEYS) repository. If you end up getting 403 errors ask a PMC member for assistance.) |
There was a problem hiding this comment.
not all committers -> only PMC members
remove link, no need to repeat it so many times
If you end up getting a 403 error, ask on the mailing list for assistance.
src/contribute/release-guide.md
Outdated
|
|
||
| #### Register to PyPI | ||
|
|
||
| Release manager needs to have an account with PyPI. If you need one, [register](https://pypi.python.org/pypi?%3Aaction=register_form) at PyPI. You also need to be a maintainer (or an owner) of the [apache-beam](https://pypi.python.org/pypi/apache-beam) package in order to push a new release. Ask a PMC member to add you as a maintainer. |
There was a problem hiding this comment.
Ask on the mailing list for assistance.
src/contribute/release-guide.md
Outdated
|
|
||
| ### Update the Python SDK version | ||
|
|
||
| In the master branch update Python SDK [version](https://github.com/apache/beam/blob/master/sdks/python/apache_beam/version.py) to the next development version (e.g. `1.2.3.dev` to `1.3.0.dev`). |
There was a problem hiding this comment.
In the master branch, update the Python SDK version identifier to the next development version.
src/contribute/release-guide.md
Outdated
|
|
||
| In the master branch update Python SDK [version](https://github.com/apache/beam/blob/master/sdks/python/apache_beam/version.py) to the next development version (e.g. `1.2.3.dev` to `1.3.0.dev`). | ||
|
|
||
| In the release branch update the Python SDK version to the release version (e.g. `1.2.3.dev` to `1.2.3`). |
There was a problem hiding this comment.
In the release branch, update
src/contribute/release-guide.md
Outdated
| * all artifacts to be deployed to the Maven Central Repository [4], | ||
| * source code tag "v1.2.3-RC3" [5], | ||
| * website pull request listing the release and publishing the API reference manual [6]. | ||
| * python artifacts are deployed along with the source release to to dist.apache.org [2]. |
src/contribute/release-guide.md
Outdated
|
|
||
| ### Deploy Python artifacts to PyPI | ||
|
|
||
| 1. Create a new release and upload python zip file for the new release using [PyPI UI] (https://pypi.python.org/pypi/apache-beam) |
There was a problem hiding this comment.
the Python zip file
the PyPI UI
src/contribute/release-guide.md
Outdated
| ### Deploy Python artifacts to PyPI | ||
|
|
||
| 1. Create a new release and upload python zip file for the new release using [PyPI UI] (https://pypi.python.org/pypi/apache-beam) | ||
| 1. Alternatively use the command line tool to upload the new release `twine upload apache-beam-${VERSION}.zip` |
src/contribute/release-guide.md
Outdated
| * Website pull request to [list the release]({{ site.baseurl }}/use/releases/) and publish the [API reference manual]({{ site.baseurl }}/documentation/sdks/javadoc/) merged | ||
| * Release tagged in the source code repository | ||
| * Release version finalized in JIRA | ||
| * Release version finalized in JIRA. (Note: Not all committers have administrator access to JIRA. If you end up getting permissions errors ask a PMC member for assistance.) |
|
Thank you @davorbonaci. Updated PR, PTAL. |
|
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id 0d55ccb with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
4 participants
R: @sb2nov @davorbonaci