[jira] [Assigned] (FLINK-31572) Other announcements
[ https://issues.apache.org/jira/browse/FLINK-31572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-31572: --- Assignee: Qingsheng Ren (was: Jing Ge) > Other announcements > --- > > Key: FLINK-31572 > URL: https://issues.apache.org/jira/browse/FLINK-31572 > Project: Flink > Issue Type: Sub-task >Reporter: Matthias Pohl >Assignee: Qingsheng Ren >Priority: Major > > h3. Recordkeeping > Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] > to seed the information about the release into future project reports. > (Note: Only PMC members have access report releases. If you do not have > access, ask on the mailing list for assistance.) > h3. Flink blog > Example: > https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/ > h3. Social media > Tweet, post on Facebook, LinkedIn, and other platforms. Ask other > contributors to do the same. > h3. Flink Release Wiki page > Add a summary of things that went well or that went not so well during the > release process. This can include feedback from contributors but also more > generic things like the release have taken longer than initially anticipated > (and why) to give a bit of context to the release process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-31572) Other announcements
[ https://issues.apache.org/jira/browse/FLINK-31572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge reassigned FLINK-31572: --- Assignee: Jing Ge (was: Qingsheng Ren) > Other announcements > --- > > Key: FLINK-31572 > URL: https://issues.apache.org/jira/browse/FLINK-31572 > Project: Flink > Issue Type: Sub-task >Reporter: Matthias Pohl >Assignee: Jing Ge >Priority: Major > > h3. Recordkeeping > Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink] > to seed the information about the release into future project reports. > (Note: Only PMC members have access report releases. If you do not have > access, ask on the mailing list for assistance.) > h3. Flink blog > Example: > https://flink.apache.org/2023/11/29/apache-flink-1.17.2-release-announcement/ > h3. Social media > Tweet, post on Facebook, LinkedIn, and other platforms. Ask other > contributors to do the same. > h3. Flink Release Wiki page > Add a summary of things that went well or that went not so well during the > release process. This can include feedback from contributors but also more > generic things like the release have taken longer than initially anticipated > (and why) to give a bit of context to the release process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FLINK-31572) Other announcements
[
https://issues.apache.org/jira/browse/FLINK-31572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qingsheng Ren reassigned FLINK-31572:
-
Assignee: Qingsheng Ren
> Other announcements
> ---
>
> Key: FLINK-31572
> URL: https://issues.apache.org/jira/browse/FLINK-31572
> Project: Flink
> Issue Type: Sub-task
>Reporter: Matthias Pohl
>Assignee: Qingsheng Ren
>Priority: Major
>
> h3. Recordkeeping
> Use [reporter.apache.org|https://reporter.apache.org/addrelease.html?flink]
> to seed the information about the release into future project reports.
> (Note: Only PMC members have access report releases. If you do not have
> access, ask on the mailing list for assistance.)
> h3. Flink blog
> Major or otherwise important releases should have a blog post. Write one if
> needed for this particular release. Minor releases that don’t introduce new
> major functionality don’t necessarily need to be blogged (see [flink-web PR
> #581 for Flink 1.15.3|https://github.com/apache/flink-web/pull/581] as an
> example for a minor release blog post).
> Please make sure that the release notes of the documentation (see section
> "Review and update documentation") are linked from the blog post of a major
> release.
> We usually include the names of all contributors in the announcement blog
> post. Use the following command to get the list of contributors:
> {code}
> git log --pretty="%an%n%cn" .. | sort | uniq | tr "\n"
> "," | sed 's/,/, /g'
> {code}
> h3. Social media
> Tweet, post on Facebook, LinkedIn, and other platforms. Ask other
> contributors to do the same.
> h3. Flink Release Wiki page
> Add a summary of things that went well or that went not so well during the
> release process. This can include feedback from contributors but also more
> generic things like the release have taken longer than initially anticipated
> (and why) to give a bit of context to the release process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
