We've been fairly hard at work in CiviCRM land resolving all the issues related to v1.5 which can be found here:
http://issues.civicrm.org/jira/secure/IssueNavigator.jspa?mode=hide&requ...
the CiviCRM 1.5 feature list is available at:
http://wiki.civicrm.org/confluence/display/CRM/CiviCRM+v1.5
We are fairly pleased with the stability of v1.4 and hope to continue the tradition of high quality releases meeting the needs of the community with v1.5. Personally I think that v1.5 has the most feature additions / improvements since v1.0beta :)
Now is a great time for folks to take a look at whats coming in v1.5 and make sure that we have not missed any important things / issues. If so, please do start a discussion on our mailing list
lobo
Comments
Any Timeline?
Lobo -
Any timeline on the release? Just upgraded several of my modules to get the most out of 1.4.
For that matter, any ideas about backwards compatibility?
M
timeline ..
we hope to get alpha tarballs out sometime later next week. Most of the api's have remained the same, there's a lot of new functionality and not too many changes to old sutff (or so i think)
lobo
Major complaints addressed?
I'm not a CiviCRM user myself but the two major complaints I've been getting are:
I wonder if any of these complaints are being addressed in CiviCRM 1.5.
major complaints ...
hey dries:
thanx for the feedback:
with regard to the issues u've raised:
CiviCRM works under multiple CMS's (Drupal, Joomla, Mambo currently). As such we make a strong attempt to be good citizens of all of them, but i suspect will never match the underlying CMS completely. I'd be interested in hearing more specific details of where the UI differs from Drupal, i suspect we could fix a fair number of those issues if we are made aware of them
I'd agree CiviCRM is fairly complex (or bloated as some might put it). However I think our goals are to be a fairly comprehensive toolkit for our user base (membership, advocacy and non-profit organizations). I suspect we are headed down the path of more features rather than being lightweight. I do agree that we need to look at both memory and performance a bit more in the next release.
lobo
Suggestions: 1. CiviCRM themes; 2. CiviCRM user cases/scenarios
1. CiviCRM themes
Not personally knowing/understanding how complicated this might be (I'm a Drupal user, not a developer), I would suggest different CiviCRM themes for the different CMS downloads (e.g., Drupal, Joomla, Mambo, etc.) so that the main CiviCRM download (e.g., CiviCRM 1.5) and the underlying CMS (e.g., Drupal 4.7.3) have a more similar look and feel.
If it's too difficult to create/maintain the different CiviCRM themes for the different CMSs, then yes, I agree that CiviCRM "will never match the underlying CMS completely" or even come close. CiviCRM and the underlying CMS don't have to match "completely," but getting them to look a bit more similar would be helpful, IMO.
2. CiviCRM user cases/scenarios
Dries wrote:
I think what he's trying to say is that the issue IS NOT "performance or memory usage". Rather, the issue, from what he's heard, IS "functionality and learning curve."
Regardless, my suggestion is to create user cases/scenarios where you showcase some of CiviCRM's different functions. For example, take some of your clients who are light, medium, and heavy CiviCRM users. Demonstrate in detail and by listing the specific CiviCRM functions each light, medium, and heavy user uses for their respective web sites. Try to make it as easy as possible for potential CiviCRM users to "visualize" themselves actually using the software by letting the potential CiviCRM users see themselves in the place of your actual clients. Give real-world examples of how CiviCRM features provide real-world benefits to solve real-world problems.
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing