struts-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From git-site-r...@apache.org
Subject [struts-site] branch asf-site updated: Updates production by Jenkins
Date Wed, 06 Dec 2017 06:30:47 GMT
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/struts-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 8ecb413  Updates production by Jenkins
8ecb413 is described below

commit 8ecb413fafd4bff9c92fabde94eb8ff5dc837884
Author: jenkins <builds@apache.org>
AuthorDate: Wed Dec 6 06:30:46 2017 +0000

    Updates production by Jenkins
---
 content/kickstart.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/kickstart.html b/content/kickstart.html
index 623b44d..a972e54 100644
--- a/content/kickstart.html
+++ b/content/kickstart.html
@@ -197,7 +197,7 @@
   Using our example, the next distribution would be labeled 2.0.43, even if version 2.0.42
was never officially
   released.</p>
 
-<p>Often. we will first grade a release as a “beta”, and invite other users to
test it too. If this second
+<p>Often we will first grade a release as a “beta”, and invite other users to test
it too. If this second
   round of beta testing goes well, then we may mark the release “General Availability”.
   Usually, that designation would also make it the new “Best Available” release. In this
case, we don’t create
   another distribution, but simply adjust the status of the same set of bits that people
have been testing all along.</p>

-- 
To stop receiving notification emails like this one, please contact
['"commits@struts.apache.org" <commits@struts.apache.org>'].

Mime
View raw message