You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@commons.apache.org by bu...@apache.org on 2017/09/24 16:27:58 UTC
svn commit: r1018631 - in /websites/staging/commons/trunk/content: ./
releases/moving-to-dormant.html
Author: buildbot
Date: Sun Sep 24 16:27:58 2017
New Revision: 1018631
Log:
Staging update by buildbot for commons
Modified:
websites/staging/commons/trunk/content/ (props changed)
websites/staging/commons/trunk/content/releases/moving-to-dormant.html
Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Sep 24 16:27:58 2017
@@ -1 +1 @@
-1809509
+1809525
Modified: websites/staging/commons/trunk/content/releases/moving-to-dormant.html
==============================================================================
--- websites/staging/commons/trunk/content/releases/moving-to-dormant.html (original)
+++ websites/staging/commons/trunk/content/releases/moving-to-dormant.html Sun Sep 24 16:27:58 2017
@@ -233,7 +233,7 @@
<li>Better alternatives are available either as open source libraries or in newer releases of the JDK</li>
</ul>
- To move a component to dormangt a number of thinks have to be taken care of.
+ To move a component to dormant a number of thinks have to be taken care of.
This page explains what is necessary to move a proper component to dormant.
@@ -261,7 +261,7 @@
So please cast your votes:
This vote will close no sooner that 72 hours from now,
- i.e. after 21:30CET 14 March 2014
+ i.e. after 21:30 UTC 14 March 2014 [Please only use UTC!]
[ ] +1 Move Commons Foo to dormant
[ ] +/-0 I'm undecided on this concern