mahout-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r890956 - in /websites/staging/mahout/trunk/content: ./ general/downloads.html
Date Wed, 18 Dec 2013 20:55:42 GMT
Author: buildbot
Date: Wed Dec 18 20:55:42 2013
New Revision: 890956

Staging update by buildbot for mahout

    websites/staging/mahout/trunk/content/   (props changed)

Propchange: websites/staging/mahout/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 18 20:55:42 2013
@@ -1 +1 @@

Modified: websites/staging/mahout/trunk/content/general/downloads.html
--- websites/staging/mahout/trunk/content/general/downloads.html (original)
+++ websites/staging/mahout/trunk/content/general/downloads.html Wed Dec 18 20:55:42 2013
@@ -358,8 +358,11 @@
     <p><a name="Downloads-OfficialRelease"></a></p>
 <h1 id="official-release">Official Release</h1>
 <p>Apache Mahout is an official Apache project and thus available from any of
-the Apache mirrors.</p>
-<p>The latest Mahout release is available for download at: <a href=""></a>.</p>
+the Apache mirrors. The latest Mahout release is available for download at: </p>
+<li><a href="">Download Latest</a></li>
+<li><a href="">Release Archive</a></li>
 <p><a href="../developers/system-requirements.html">MAHOUT:System Requirements</a>
  are detailed online. </p>
 <p>For Maven users please include the following snippet in your pom:</p>
@@ -390,53 +393,12 @@ the Apache mirrors.</p>
 <p>In case you are using Ivy, Gradle, Buildr, Grape or SBT you might want to directly
head over to the official <a href="">Maven
Repository search</a>.</p>
-<p><a name="Downloads-SnapshotReleases"></a></p>
-<h1 id="snapshot-releases">Snapshot Releases</h1>
-<p>Recent builds are available on the Apache Jenkins <a href="">build
-To get the latest, navigate to "Build History", in the lower left-hand
-Pick the latest build which has a yellow ball instead of a red ball.
-Go to "Build Artifacts" page.
-Download "all files in trunk" zip file</p>
-<p>Now, how you go from there to running examples: you don't. These build
-artifacts do not include the shell scripts and other materiel needed
-to run the Mahout examples: you are only able to use the jars in your
-own projects.</p>
-<p><a href="">MAHOUT-935</a>
- is filed as a marker to make the builds more useable. You are welcome and
-encouraged to fix this problem!</p>
 <p><a name="Downloads-FutureReleases"></a></p>
 <h1 id="future-releases">Future Releases</h1>
 <p>Official releases are usually created when the developers feel there are
 sufficient changes, improvements and bug fixes to warrant a release. Watch
 the <a href="">Mailing lists</a>
  for latest release discussions.</p>
-<p><a name="Downloads-Backwardscompatibilityofreleases"></a></p>
-<h1 id="backwards-compatibility-of-releases">Backwards compatibility of releases</h1>
-<p><em>Please note that below backwards compatibility contract is a draft. As
-soon as finished the line you are about to read will be deleted.</em></p>
-<p>As of version 1.0 Apache Mahout will provide the following backwards
-compatibility guarantees.</p>
-<p><a name="Downloads-Datainputformats,Modelformats,Modeloutput"></a></p>
-<h2 id="data-input-formats-model-formats-model-output">Data input formats, Model formats,
Model output</h2>
-<p>All minor versions within a major release can read prior versions data
-within the same major release.  That is, 3.4 can read a 3.3 data.  However,
-3.3 cannot read a 3.4 data file.  When a user reads 3.3 data w/ 3.4, it is
-silently upgraded to 3.4.</p>
-<p>A major TODO that you can help with if you are interested is to provide
-serialization methods based on <a href="">Apache Avro</a>
- that would make support for input, output and model format upgrade easier.</p>
-<p>Another option is to use the <a href="">SequenceFile.Metadata</a>
- feature to store file format versions.</p>
-<p><a name="Downloads-APIsandcommandlinescripts"></a></p>
-<h2 id="apis-and-command-line-scripts">APIs and command line scripts</h2>
-<p>For APIs, we typically mark things as @mahout.experimental if we think they
-may change within minor releases.  We also mark things as deprecated that
-are going away.  Deprecated items are then removed on the next major
-release.  The upgrade path is usually to go to x.9, remove all deprecations
-and then go to x+1.0.</p>
-<p>We also communicate to users via release notes when we purposefully broke
-back compat.</p>

View raw message