You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by gi...@apache.org on 2020/09/26 22:55:36 UTC
[groovy-dev-site] branch asf-site updated: 2020/09/26 22:55:31:
Generated dev website from groovy-website@3fa9576
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-dev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 3ad920d 2020/09/26 22:55:31: Generated dev website from groovy-website@3fa9576
3ad920d is described below
commit 3ad920dcebfb04db26aa69650c9d521e32ba8e69
Author: jenkins <bu...@apache.org>
AuthorDate: Sat Sep 26 22:55:31 2020 +0000
2020/09/26 22:55:31: Generated dev website from groovy-website@3fa9576
---
wiki/groovy-release-discussion.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/wiki/groovy-release-discussion.html b/wiki/groovy-release-discussion.html
index ba87ee6..b5d33c2 100644
--- a/wiki/groovy-release-discussion.html
+++ b/wiki/groovy-release-discussion.html
@@ -280,7 +280,7 @@ Many of the ideas went into Groovy’s current release process which involve
</ul>
</div>
<div class="paragraph">
-<p><em>We need to add the <strong>DISCLAIMER</strong>. The "incubating" part is disturbing. In particular, Groovy is not a new project. It’s been there for 12 years, and the last release before Apache will be 2.4.2. Does it mean that the next release will have to be named 2.4.3-incubating? It will be very disturbing for our users, and it sounds pretty bad, just as if Groovy wasn’t production ready. Should we do this, then the incubation phase should be shortened as much as po [...]
+<p><em>We need to add the <strong>DISCLAIMER</strong>. The "incubating" part is disturbing. In particular, Groovy is not a new project. It has been around for 12+ years, and the last release before Apache will be 2.4.2. Does it mean that the next release will have to be named 2.4.3-incubating? It will be very disturbing for our users, and it sounds pretty bad, just as if Groovy wasn’t production ready. Should we do this, then the incubation phase should be shortened as much as poss [...]
</div>
<div class="ulist">
<ul>