*Enterprise Edition (EE)* , , are available from Pentaho
*Pentaho Community Edition (CE)*_ software is high quality community supported software. Although community support is very good, there is no obligation to answer questions or provide timely answers. You are responsible for your own success which will require time, effort and a small amount of technical ability. If you prefer to have a relationship with a known vendor who will answer questions over the phone, help you during your evaluation and support you in production; please visit www.pentaho.com.
*Pentaho Community Edition (CE)* software is available in three forms: [source code|http://en.wikipedia.org/wiki/Sourcecode] that you can [build|http://en.wikipedia.org/wiki/Software_build] yourself, [continuous integration|http://en.wikipedia.org/wiki/Continuous_integration] (CI) builds and [released|http://en.wikipedia.org/wiki/Software_release] builds.
*Source code* is available from our [Subersion|http://en.wikipedia.org/wiki/Subversion_(software)] (SVN) repository ([Perforce|http://en.wikipedia.org/wiki/Perforce] for mondrian) and may be freely downloaded. Information about how to get the code can be found [here|http://community.pentaho.com/getthecode/]. Instructions for building a project can be found on that project's home page. Source code is continuously being modified in the [trunk|http://en.wikipedia.org/wiki/Trunk_(software)] and may not compile for short periods of time while other supporting files are checked in. [Branches|http://en.wikipedia.org/wiki/Branching_(software)] and [tagged|http://en.wikipedia.org/wiki/Revision_tag] snapshots are available for building the source from a known state. Building from source is advanced and should be performed by someone with development experience.
*CI builds* are managed by [Hudson|http://en.wikipedia.org/wiki/Hudson_(software)], the continuous integration tool used by Pentaho. Hudson automatically rebuilds the project after new code for that project is checked into version control. It verifies that the project can still be compiled and assembled. The dynamic nature of CI builds makes the quality of any specific build unpredictable. You should only be using CI builds if you know that a bug or feature was implemented in a specific CI build and you want to test it. From time to time, a known stable CI build may be identified and made generally available to the community for testing purposes. The Hudson server is located at [ci.pentaho.com|http://ci.pentaho.com].
*Released builds* are official builds, compiled and assembled by Pentaho [CM|http://en.wikipedia.org/wiki/Configuration_management#Software_configuration_management|Configuration Management] at a predetermined point in time. Released builds are hosted on [SourceForge.net|http://sourceforge.net]. SourceForge.net is the world's largest open source software development web site. More information about SourceForge.net can be found [here|http://apps.sourceforge.net/trac/sourceforge/wiki/What%20is%20SourceForge.net?]. Pentaho software is hosted under four different SourceForge projects: *[*pentaho*|http://sourceforge.net/projects/pentaho|Pentaho BI Server, Kettle, Report Designer, Metadata Editor and Design Studio]*, *[*mondrian*|http://sourceforge.net/projects/mondrian|Mondrian, Schema Designer and Agg Designer]*, *[*jfreereport*|http://sourceforge.net/projects/JFreeReport|Reporting Engine and supporting sub projects]* and *[*weka*|http://sourceforge.net/projects/weka|Data mining]*. Released builds are identified as a Milestone, Release Candidate or stable.
*Milestone (M)* builds occur throughout the development cycle when a significant set of features or bugs have been implemented. The build will be stable enough for testing those new changes but may have introduced new bugs or instabilities to other parts of the code. Milestones give the community an opportunity to provide feedback on a feature while there is still time to change it during that dev cycle. Milestone builds should never be put into production.
*Release candidate (RC)* builds are much more stable then milestones and come at the end of the dev cycle. There can be as many RC builds (but usually only 2) as needed until the release is considered stable. Theoretically, a release candidate could be promoted to stable without changing any code (I have never seen this actually happen.) RC builds are ready for full testing and give the community time to find critical bugs or usability issues before the release is marked stable. RC builds should not be put into production but can be used for acceptance testing.
*Stable* builds are posted after a series of RC builds and when the consensus is that the release has no blocking issues. The stable build is usually the last CE build in a release. Pentaho does not post patch builds for CE except in extreme cases. If you are going to put a CE release into production, you will want to use a stable build.
Released builds of the Pentaho Open Source BI Suite - Community Edition (CE) software is hosted on [SourceForge.net|http://sourceforge.net]. SourceForge.net is the world's largest open source software development web site. More information about SourceForge.net can be found [here|http://apps.sourceforge.net/trac/sourceforge/wiki/What%20is%20SourceForge.net?]. Navigating SourceForge.net can be intimidating and a little confusing. This should help you find the software you are looking for.
Released builds of the Pentaho Open Source BI Suite - Community Edition (CE) software is hosted on [SourceForge.net|http://sourceforge.net]. SourceForge.net is the world's largest open source software development web site. More information about SourceForge.net can be found