Step up and help out!CiviCRM 3.0 alpha release is a great occasion to get involved in CiviCRM community. There are many ways you can help make this release better and bug free.
- Log in to CiviCRM 3.0 public sandbox and try out your favourite features. If you find a problem, please report it on the appropriate board of our forum. Remember that sandbox data is periodically reset.
- Download the tarball and upgrade a copy of your site to 3.0 - let us know if you encounter any problems. This is an especially valuable contribution since we need to have the upgrade process tested on different sets of data. After you've done this, play around with your favourite features, with your local data. Problems appearing? Use the CiviCRM 3.0 alpha testing board on the forums to discuss problems and find answers!
- Go through the CiviCRM 3.0 Documentation, help us improve it and make it relevant to upcoming version before we reach beta state (estimated 3 weeks). It's a wiki, so after creating an account, you can fix problems and add missing information.
- If you're a developer and have PHP skills, you can submit a patch through our issue tracker. Just create an issue, attaching a patch file that fixes a problem you've discovered in the CiviCRM 3.0 codebase.
Existing issuesCiviCRM 3.0.alpha2 is not bug free. We know about some problems and are working hard to fix them before the next release (expect it a week from now). The list of existing issues is available here. If you notice any new problems, please report them as mentioned above.
DownloadsYou can download the release from SourceForge – select from the civicrm-latest section. The filenames include the 3.0.alpha2 label: civicrm-3.0.alpha2. Make sure you’re downloading the correct version (for Drupal, Joomla or standalone).
New InstallationsIf you are installing CiviCRM 3.0 alpha from scratch, please use the automated installer instructions for respective versions: Drupal, Joomla and Standalone. Please note that at the alpha stage, the documentation might not be accurate and refers more to previous version. We are counting on your contributions to make it fully adequate before 3.0 beta is available!
Upgrading from 2.* seriesAn automated upgrade process is included in the alpha release, and the procedure for upgrading to 3.0.alpha2 is the same as for upgrading 2.1.x and 2.2.x versions. Instructions for upgrading for two CMS types (Drupal and Joomla) and Standalone are provided. We will continue to include automated upgrades for subsequent alpha and beta releases of 3.0 – so you should be able to upgrade your test site easily over the course of the release cycle.
Actually, the real question is about a svn. is there a way to know when/if the db structure needs to be modified, and a simple way of doing just the right alter instead of having to trash+recreate the complete db ?
just use civicrm/upgrade?reset=1 and the incremental upgrader does the right thing
upgrading from svn is a bit harder :(
Set the right version in civicrm-version.txt. update to the latest tagged version and then do a civicrm/upgrade?reset=1
upgrading in the middle of a release week is a bit dangerous. you can check the php/sql code at