You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by wu...@apache.org on 2020/03/23 06:55:49 UTC

[skywalking] branch new-release-doc created (now d125a23)

This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a change to branch new-release-doc
in repository https://gitbox.apache.org/repos/asf/skywalking.git.


      at d125a23  Update the announce process.

This branch includes the following new commits:

     new d125a23  Update the announce process.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[skywalking] 01/01: Update the announce process.

Posted by wu...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

wusheng pushed a commit to branch new-release-doc
in repository https://gitbox.apache.org/repos/asf/skywalking.git

commit d125a23896d72f8ce124b627be1ee386895f8645
Author: Wu Sheng <wu...@foxmail.com>
AuthorDate: Mon Mar 23 14:55:19 2020 +0800

    Update the announce process.
---
 docs/en/guides/How-to-release.md | 37 ++++++++++++++++++++++++-------------
 1 file changed, 24 insertions(+), 13 deletions(-)

diff --git a/docs/en/guides/How-to-release.md b/docs/en/guides/How-to-release.md
index f96b6d5..c9bd8b8 100644
--- a/docs/en/guides/How-to-release.md
+++ b/docs/en/guides/How-to-release.md
@@ -242,35 +242,46 @@ enter your apache password
 We only publish Apache mirror path as release info.
 4. Public asc and sha512 locate in `https://www.apache.org/dist/skywalking/x.y.z/xxx`
 5. Public KEYS pointing to  `https://www.apache.org/dist/skywalking/KEYS`
-6. Send ANNOUNCE mail to `dev@skywalking.apache.org`.
+6. Update website download page. http://skywalking.apache.org/downloads/ . Include new download source, distribution, sha512, asc and document
+links. Links could be found by following above rules(3)-(6).
+7. Add a release event on website homepage and even page. Announce the public release with changelog or key features.
+8. Send ANNOUNCE mail to `dev@skywalking.apache.org`, `	announce@apache.org`, the sender should use Apache mail.
 ```
-Mail title: [ANNOUNCE] Release Apache SkyWalking version x.y.z
+Mail title: [ANNOUNCE] Apache SkyWalking x.y.z released
 
 Mail content:
 Hi all,
 
 Apache SkyWalking Team is glad to announce the first release of Apache SkyWalking x.y.z.
 
-SkyWalking: APM (application performance monitor) tool for distributed systems, 
-especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures. 
+SkyWalking: APM (application performance monitor) tool for distributed systems,
+especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures.
+
+This release contains a number of new features, bug fixes and improvements compared to
+version a.b.c(last release). The notable changes since x.y.z include:
+
+(Highlight key changes)
+1. ...
+2. ...
+3. ...
 
-Vote Thread: 
+Please refer to the change log for the complete list of changes:
+https://github.com/apache/skywalking/blob/v7.0.0/CHANGES.md
 
-Download Links : http://skywalking.apache.org/downloads/
+Apache Tomcat website:
+http://skywalking.apache.org/
 
-Release Notes : https://github.com/apache/skywalking/blob/x.y.z/CHANGES.md
+Downloads:
+http://skywalking.apache.org/downloads/
 
-Website: http://skywalking.apache.org/
+Twitter:
+https://twitter.com/ASFSkyWalking
 
 SkyWalking Resources:
+- GitHub: https://github.com/apache/skywalking
 - Issue: https://github.com/apache/skywalking/issues
 - Mailing list: dev@skywalkiing.apache.org
-- Documents: https://github.com/apache/skywalking/blob/x.y.z/docs/README.md
 
 
 - Apache SkyWalking Team
 ```
-
-7. Update website download page. http://skywalking.apache.org/downloads/ . Include new download source, distribution, sha512, asc and document
-links. Links could be found by following above rules(3)-(6).
-8. Add a release event on website homepage and even page. Announce the public release with changelog or key features.