Good day, folks,
The CiviCRM Partners list recently discussed the topic of release-announcements and release-testing. We'd like to treat 4.4.6 as a bit of an experiment to address two specific ideas about release-management:
- To allow system-implementers to allocate time/resources to handle upgrades promptly, we should provide specific, advanced notification about upcoming releases.
- To allow testing of the new release against real databases and real use-cases, we should provide a real, installable tarball before the final release announcement.
For this experiment with 4.4.6, we're providing a "release candidate" one week before the official announcement (scheduled for Wed, Jul 2). The hope is that this week can provide lead-time (to arrange logistics of upgrades) and provide testing-time (for anyone who wants 4.4.6 to be stable).
4.4.6 includes only critical bug-fixes and has been internally tested. However, even with limited changes, there's a risk of unintended side-effects and regressions. Based on the specific changes in 4.4.6, there are a few "at-risk" areas where you may want to test:
- Screens which use profile forms
- Upload and display of contact images
- Concurrent delivery of scheduled CiviMail blasts
For downloads and other details, please see:
