The team has been working hard to fix issues and bugs reported by the community - and a second beta release of CiviCRM 2.0 is now available for download on SourceForge.
We strongly encourage folks to download and test the beta. If you have an existing CiviCRM install - please upgrade a test copy of your site. Your efforts are critical to help ensure a smooth transition and a quality final release. We especially need folks with existing Joomla installs to (re)test the upgrade process as we've fixed a number of issues there.
If you've already installed the initial 2.0 beta distribution - and have reported issues - please take the time to install beta 2 and verify that your issues have been resolved. There were no database changes from beta 1 to beta 2 - so you can simply over-write the beta 1 codebase.
I've included a listing of the 30 issues which were resolved between beta 1 and beta 2 below. You can see the current list of remaining open issues here.
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
Now that v2.0 has hit beta, its time for us to start thinking (and working) on v2.1. Yes, I know many of you have not yet downloaded v2.0 beta. Please consider downloading and testing the release NOW. This help us release a higher quality product :)
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.
If you've implemented CiviCRM, please consider adding a case study to http://wiki.civicrm.org/confluence/display/CRMDOC/Case+Studies or the forums at http://forum.civicrm.org/index.php/board,4.0.html. It would be great if you could include detailed descriptions of the implementation (custom fields used, profiles, special menus created for tasks) as well as obstacles, work-arounds, "results".
Dave Greenberg sent this to the civicrm-dev list, but I don't see it in the blog so I'm posting his message here. -- Judy Hallman
If you're attending (or thinking about attending) NTEN's Non-profit Technology Conference in New Orleans this March - check out these CiviCRM related happenings...
******************************************************** Developer Bootcamp - March 18-19 in New Orleans ********************************************************
After 2.5 weeks in India, the Polish team is happy (hmm...?) to report safe landing in Warsaw last Tuesday. :-) We spent the first two weeks in Mumbai, hanging out with our mates from the India team, and with Lobo. Before that, I had the opportunity to meet only some members of the team, during other travels. It was the first time, when (almost) the whole group was gathered in a single physical space.
Last week we got some feedback on the dynamic Contact Search feature - in the form of a bug report. The topic was "Autofill is too aggressive". The search box was being auto-filled based on the first few letters typed - and the auto-filling was often NOT helpful. It sometimes jumped ahead and completed the field with a different name then the one they were looking for.
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.
Earlier this week I had an opportunity to meet with folks at the Glide Foundation in San Francisco. Glide "empowers San Francisco’s poor and disenfranchised to make meaningful changes in their lives to break the cycle of poverty and dependence" by providing an amazing range of programs from meals to housing, health services, employment training and more.
We are excited to announce that our 2.0 Alpha release is now available for download here
You can also try it out on our sandbox site here
This release 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 release and help improve the final product
You can view Release Highlights here
The resolved issues list sports the implementation details and lists fixed bugs. Sandbox We've setup a public sandbox. The sandbox is a great way to "try out" the new features while helping us test the release. We will update this over time as we fix the remaining open and new issues. Downloads You can download the release here. Select from the civicrm-latest section. The filenames include the 2.0 Alpha label: civicrm-2.0.alpha…. Be sure and download the correct version for your CMS (Drupal or Joomla). As announced previously, 1.9 and all subsequent versions of CiviCRM require PHP 5.x and MySQL 5.x. PHP 4 is no longer supported. New Installations If you are installing CiviCRM 2.0 Alpha from scratch, please use the automated installater instructions linked below (these are for CiviCRM 1.9, but shouldn't change): Drupal and Joomla. Upgrading from 1.9 If you are upgrading an existing 1.9 site (working with a copy of the site, of course), we have provided a upgrade path. Please install the new code without modifying the database and access the url "q=civicrm/upgrade&reset=1". The upgrade has been tested for Drupal 5.x only. Support for Joomla will be released soon. Reporting Issues and Bugs We look forward to getting your feedback on the release in the coming days. Bugs should be reported via our issue tracking system. Please select 2.0 in the 'Affects Version' dropdown. You will need to register as a user – this ensures that we can follow-up with you on your bug reports if necessary. Please ensure that the bug you've found is not reported already; also, there still are some issues open against CiviCRM 2.0.
