- How do I get a list of contacts whose records were added in the past month - along with the name of the person who added them?
- Is there a way to export total contribution amount for a given year by Household? I want to include all contributions from individuals that are household members.
- I can't export the name of each contact's current Employer. What's the solution?
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). The forums are averaging more than 75 forums post / weekday.
CiviCRM 2.0 doesn’t only start introducing significant code oriented architecture changes, we’re also using the occasion of having a nice, round release number to introduce some new things in the process. This version is the first one where we want to announce official string freeze stage in our release process.
We are excited to announce that our 2.0 Beta release is now available for download, AND to try out on our demo site. You can find Release Highlights here, and check out the resolved issues listing for details on the 330+ improvements and bug fixes.
2.0 has significant code and schema changes to improve performance and scalability. The upgrade process is now a multi-step web-based process. We would like to encourage folks to download and test the beta release and help improve the final product. You can contribute significantly to the project by testing the upgrade process against a copy of your 1.9 data, as well as running your regular tasks on an upgraded site.
We continued with work in team strategy, helping team members to learn / share the work strategy and approach towards a problem. In last 5-6 days we have resolved 25 issues, created 29 and closed 43 issues which is the indication of better QA towards v2.0.
v2.0 has significant schema changes, and hence a simple sql script could no longer serve as our primary upgrade mechanism. We are introducing a new upgrade system in 2.0 which will run in a couple of steps and upgrade the user's database. It has been an interesting exercise to come up with the upgrade script. Here are a few things we learned as we went through the process.