[incubator] branch master updated: add requirement to have incubating in name

[jm...@apache.org]

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

jmclean pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator.git


The following commit(s) were added to refs/heads/master by this push:
     new 0839f4b  add requirement to have incubating in name
     new e979c59  Merge pull request #19 from justinmclean/master
0839f4b is described below

commit 0839f4b88df5bd0d7aa8fe71d635b1ca6d8dfbc9
Author: Justin Mclean <jm...@apache.org>
AuthorDate: Fri Jul 26 10:22:15 2019 +1000

    add requirement to have incubating in name
---
 pages/cookbook/index.ad | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/pages/cookbook/index.ad b/pages/cookbook/index.ad
index 58fdcf3..fd83396 100644
--- a/pages/cookbook/index.ad
+++ b/pages/cookbook/index.ad
@@ -182,8 +182,9 @@ governance, as it fosters project durability.
 A podling is expected to make several software releases during incubation, that gradually progress towards being
 fully conformant to the link:http://www.apache.org/legal/release-policy.html[ASF Release Policy].
 
-In addition to following that policy, podling releases must include a DISCLAIMER (TODO: link) to avoid any confusion
-as to the project's status. As podlings are not "real" ASF projects yet, it is important to set expectations right.
+In addition to following that policy, podling releases must include the word "incubating" in any release file names
+and a DISCLAIMER (TODO: link) to avoid any confusion as to the project's status. As podlings are not "real" ASF
+projects yet, it is important to set expectations right.
 
 Also, voting on podling releases happens in two phases:
 


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org