cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Update of "GettingStarted" by EricEvans
Date Mon, 30 Nov 2009 20:50:02 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "GettingStarted" page has been changed by EricEvans.
The comment on this change is: update to include links to 0.5.0 beta1.
http://wiki.apache.org/cassandra/GettingStarted?action=diff&rev1=15&rev2=16

--------------------------------------------------

  == Step 1: Picking a version ==
  At any given time, there are a number of different versions available for install:
  
-  1. Stable releases
+ === Stable releases ===
-   Cassandra stable releases are well tested and reasonably free of serious problems, (or
at least the problems are known and well documented). If you are setting up a production environment,
a stable release is what you want. 
+ Cassandra stable releases are well tested and reasonably free of serious problems, (or at
least the problems are known and well documented). If you are setting up a production environment,
a stable release is what you want. 
  
-   Download links for the latest stable release can always be found on the [[http://incubator.apache.org/cassandra/#download|website]].
+ Download links for the latest stable release can always be found on the [[http://incubator.apache.org/cassandra/#download|website]].
  
-  1. Betas and release candidates
+ === Betas and release candidates ===
-   Betas are prototype releases considered ready for user testing, and release candidates
have the potential to become the next stable release. These releases represent the state-of-the-art
so are often the best place to start, and since APIs and on-disk storage formats can change
between major versions this can also save you from an upgrade. The testing and feedback is
also highly appreciated.
+ Betas are prototype releases considered ready for user testing, and release candidates have
the potential to become the next stable release. These releases represent the state-of-the-art
so are often the best place to start, and since APIs and on-disk storage formats can change
between major versions this can also save you from an upgrade. The testing and feedback is
also highly appreciated.
  
-  1. Nightly builds
-   Nightly builds represent the current state of development as of the time of the build.
They contain all of the previous days new features, fixes, and newly introduced bugs. The
only guarantee they come with is that they successfully build and the unit tests pass. Nightly
builds are a handy way of testing recent changes, or accessing the latest features and fixes
not found in beta or release candidates, but there is some risk of them being buggy. 
+   * [[http://www.apache.org/dyn/closer.cgi?path=/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-bin.tar.gz|apache-cassandra-incubating-0.5.0-beta1-bin.tar.gz]]
[ [[http://www.apache.org/dist/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-bin.tar.gz.asc|PGP]]
] [ [[http://www.apache.org/dist/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-bin.tar.gz.md5|MD5]]
] [ [[http://www.apache.org/dist/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-bin.tar.gz.sha|SHA]]
]
+   * [[http://www.apache.org/dyn/closer.cgi?path=/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-src.tar.gz|apache-cassandra-incubating-0.5.0-beta1-src.tar.gz]]
[ [[http://www.apache.org/dist/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-src.tar.gz.asc|PGP]]
] [ [[http://www.apache.org/dist/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-src.tar.gz.md5|MD5]]
] [ [[http://www.apache.org/dist/incubator/cassandra/0.5.0/apache-cassandra-incubating-0.5.0-beta1-src.tar.gz.sha|SHA]]
]
  
-   The most recent nightly build can be downloaded [[http://hudson.zones.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/|here]].
+ When downloading from a mirror, please be sure to verify the checksums and OpenPGP compatible
signature (see the MD5, SHA1, and PGP links above). The [[http://www.apache.org/dist/incubator/cassandra/KEYS|KEYS]]
file contains the public key(s) used for signing releases. 
  
-  1. Subversion
-   Cassandra's subversion repository is where all active development takes place. Anyone
interested in contributing to the project should use a checkout of trunk. If you do run from
subversion, be sure to update frequently, and subscribe to the [[mailto:cassandra-dev-subscribe@incubator.apache.org?subject=subscribe|mailing
list]] to stay abreast of the latest developments.
+ === Nightly builds ===
+ Nightly builds represent the current state of development as of the time of the build. They
contain all of the previous days new features, fixes, and newly introduced bugs. The only
guarantee they come with is that they successfully build and the unit tests pass. Nightly
builds are a handy way of testing recent changes, or accessing the latest features and fixes
not found in beta or release candidates, but there is some risk of them being buggy. 
  
+ The most recent nightly build can be downloaded [[http://hudson.zones.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/|here]].
+ 
+ === Subversion ===
+ Cassandra's subversion repository is where all active development takes place. Anyone interested
in contributing to the project should use a checkout of trunk. If you do run from subversion,
be sure to update frequently, and subscribe to the [[mailto:cassandra-dev-subscribe@incubator.apache.org?subject=subscribe|mailing
list]] to stay abreast of the latest developments.
+ 
-   Instructions for checking out the source code can always be found on the [[http://incubator.apache.org/cassandra/#download|website]].
+ Instructions for checking out the source code can always be found on the [[http://incubator.apache.org/cassandra/#download|website]].
  
  <<Anchor(running_a_single_node)>>
  == Step 2: Running a single node ==

Mime
View raw message