Blogs
A few folks from the core CiviCRM team (dave greenberg, kurund jalmi, michal mach, yashodha chaku and lobo) are having a CiviCRM team meeting in Nelson, NZ. Our current dates are for the meetup to happen between Apr 23rd to May 4th. We could potentially do a developer and/or end user training on the weekends apr 26/27 or may 3/4. Locations could be auckland/wellington/christchurch or if a lot of interest in AU, sydney/melbourne is a possibility.
Earlier today at approx 6:00 am NZT (yes, we are early birds), we released CiviCRM v2.0-beta4. At approx 9:00 am, I saw a post from aaron about some missing files in the release. I downloaded and verified what aaron said and realized we had messed up big time :(. Our release czar piotr was offline and not reachable.
There is an interesting thread going on in the CiviCRM forum: CiviCRM is scary. This thread started off on the Progressive Exchange mailing list. You can view the archive here ( you need to be sign up to view the archives).
So some folks have complained about the paypal sandbox and the performance on the forums. PayPal has been our primary processor primarily because of its international coverage and decent api's. We set up most of this a couple years back and other than periodic testing, have not really used it too much. However with the 2.0 restructuring, we introduced a few bugs in the process and spent a bit more time on the paypal sandbox than normal.
This article covers - how to install CiviCRM v2.0 on Joomla 1.5 without Legacy support. It also provides some insight into the way components are organized and accessed through Joomla.
CiviCRM v2.0 has gotten really good community feedback and testing. We plan on having at least two more beta releases before issuing a final release. Both the forums and the issue queue have been very busy with good bugs (some of which have been there for the past couple of versions!) and great feature ideas, many of which we plan to implement in v2.1. We've already resolved more than 375 bugs in v2.0 which is close to 100 more bugs than the previous highest (282 in 1.8).