
Daily Builds are the latest copies of the installer +
CMS + Sapphire. They reflect what is currently in
Subversion. Being the most recent code, Daily
Builds are less stable.
Daily Builds are created just before midnight (GMT + 12:00) and are available from
http://dailybuilds.silverstripe.com
It's best to run the installer in a fresh location. If you just want to upgrade an already-installed SilverStripe website, then download the .tar.gz and extract cms, jsparty, and sapphire and override your existing folders. Leave the other stuff (e.g., install.php, etc.); you don't need need to copy them into your existing system.
In the source folder, and inside each tarball are a number of files called "changelog.xxxx". These are automatically generated files:
"today" shows changes that happened in the preceding 24 hours since the prior dailybuild. Sometimes this will be empty.
"sincestable" shows changes since the last stable release.
There is a seperate file for the installer, cms, sapphire, and jsparty, making it easier for you to track differences for the different areas of SilverStripe.
There's a file called silverstripe_version in the sapphire, cms, and jsparty of each tar.gz, which contains the version in the format "2.0.1-dailybuild-2007-03-28". Also, the installer looks at this file and displays it.
Want to get involved in and discuss core development?
Join our Core Developers Discussion Google Group.
Interested in knowing what happens to the SilverStripe codebase as it evolves?
Subscribe to the SilverStripe changelog RSS feed.
Want announcements of new releases to the SilverStripe codebase and modules?
Join our Release Announcements Google Group.
Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com
Comments on this website? Please give feedback.