You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/02/20 19:28:00 UTC
[jira] [Updated] (FLINK-31157) Propose a pull request for website updates
[ https://issues.apache.org/jira/browse/FLINK-31157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Pohl updated FLINK-31157:
----------------------------------
Description:
The final step of building the candidate is to propose a website pull request containing the following changes:
# update [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as required
## update version references in quickstarts ({{{}q/{}}} directory) as required
## (major only) add a new entry to {{flink_releases}} for the release binaries and sources
## (minor only) update the entry for the previous release in the series in {{flink_releases}}
### Please pay notice to the ids assigned to the download entries. They should be unique and reflect their corresponding version number.
## add a new entry to {{release_archive.flink}}
# add a blog post announcing the release in _posts
# add a organized release notes page under docs/content/release-notes and docs/content.zh/release-notes (like [https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]). The page is based on the non-empty release notes collected from the issues, and only the issues that affect existing users should be included (e.g., instead of new functionality). It should be in a separate PR since it would be merged to the flink project.
(!) Don’t merge the PRs before finalizing the release.
----
h3. Expectations
* Website pull request proposed to list the [release|http://flink.apache.org/downloads.html]
* (major only) Check {{docs/config.toml}} to ensure that
** the version constants refer to the new version
** the {{baseurl}} does not point to {{flink-docs-master}} but {{flink-docs-release-X.Y}} instead
was:
The final step of building the candidate is to propose a website pull request containing the following changes:
# update [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as required
## update version references in quickstarts ({{q/}} directory) as required
## (major only) add a new entry to {{flink_releases}} for the release binaries and sources
## (minor only) update the entry for the previous release in the series in {{flink_releases}}
### Please pay notice to the ids assigned to the download entries. They should be unique and reflect their corresponding version number.
## add a new entry to {{release_archive.flink}}
# add a blog post announcing the release in _posts
# add a organized release notes page under docs/content/release-notes and docs/content.zh/release-notes (like https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/). The page is based on the non-empty release notes collected from the issues, and only the issues that affect existing users should be included (e.g., instead of new functionality). It should be in a separate PR since it would be merged to the flink project.
(!) Don’t merge the PRs before finalizing the release.
> Propose a pull request for website updates
> ------------------------------------------
>
> Key: FLINK-31157
> URL: https://issues.apache.org/jira/browse/FLINK-31157
> Project: Flink
> Issue Type: Sub-task
> Reporter: Matthias Pohl
> Priority: Major
>
> The final step of building the candidate is to propose a website pull request containing the following changes:
> # update [apache/flink-web:_config.yml|https://github.com/apache/flink-web/blob/asf-site/_config.yml]
> ## update {{FLINK_VERSION_STABLE}} and {{FLINK_VERSION_STABLE_SHORT}} as required
> ## update version references in quickstarts ({{{}q/{}}} directory) as required
> ## (major only) add a new entry to {{flink_releases}} for the release binaries and sources
> ## (minor only) update the entry for the previous release in the series in {{flink_releases}}
> ### Please pay notice to the ids assigned to the download entries. They should be unique and reflect their corresponding version number.
> ## add a new entry to {{release_archive.flink}}
> # add a blog post announcing the release in _posts
> # add a organized release notes page under docs/content/release-notes and docs/content.zh/release-notes (like [https://nightlies.apache.org/flink/flink-docs-release-1.15/release-notes/flink-1.15/]). The page is based on the non-empty release notes collected from the issues, and only the issues that affect existing users should be included (e.g., instead of new functionality). It should be in a separate PR since it would be merged to the flink project.
> (!) Don’t merge the PRs before finalizing the release.
>
> ----
> h3. Expectations
> * Website pull request proposed to list the [release|http://flink.apache.org/downloads.html]
> * (major only) Check {{docs/config.toml}} to ensure that
> ** the version constants refer to the new version
> ** the {{baseurl}} does not point to {{flink-docs-master}} but {{flink-docs-release-X.Y}} instead
--
This message was sent by Atlassian Jira
(v8.20.10#820010)