svn commit: r916962 - in /websites/staging/sling/trunk/content: ./ downloads.html

[bu...@apache.org]

Author: buildbot
Date: Mon Jul 21 14:38:02 2014
New Revision: 916962

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/downloads.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 21 14:38:02 2014
@@ -1 +1 @@
-1611639
+1612282

Modified: websites/staging/sling/trunk/content/downloads.html
==============================================================================
--- websites/staging/sling/trunk/content/downloads.html (original)
+++ websites/staging/sling/trunk/content/downloads.html Mon Jul 21 14:38:02 2014
@@ -212,6 +212,12 @@ incubator releases of Apache Sling, have
 <td>A p2 update site which can be installed in Eclipse.</td>
 <td><a href="[preferred]/sling/eclipse/1.0.0">Update site</a> <a href="[preferred]/sling/org.apache.sling.ide.p2update-1.0.0.zip">(zip download)</a> (<a href="http://www.apache.org/dist/sling/org.apache.sling.ide.p2update-1.0.0.zip.asc">asc</a>, <a href="http://www.apache.org/dist/sling/org.apache.sling.ide.p2update-1.0.0.zip.md5">md5</a>)</td>
 </tr>
+<tr>
+<td>You can also use <a href="[preferred]/sling/eclipse">the stable update site</a>, which always points to the latest version. This is the simplest way of ensuring that you stay up to date with the latest version.</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
 </tbody>
 </table>