The second release candidate of Drupal 4.7 is now available. 55 more issues have been fixed since RC1. No known critical issues remain, so unless new major problems arise, this will be the last release candidate before Drupal 4.7.0 final.
Please test this latest release, so that 4.7.0 will be a trouble-free ride for everyone.
If you maintain a contributed module or theme, now is definitely the time to ensure your contribution works with Drupal 4.7. The Module Upgrading Guide and Theme Upgrading Guide contain a list of all required changes. Make sure there are no last-minute changes that you missed.
Drupal 4.7 RC2 can be downloaded at http://drupal.org/files/projects/drupal-4.7.0-rc2.tar.gz.
More info at: http://drupal.org/drupal-4.7.0-rc2
Steven Wittens
Steven Wittens wrote:
The second release candidate of Drupal 4.7 is now available.
I am thinking of upgrading my 4.6.6 drupal site to 4.7.rc2, but since I am using several modules.. I am wondering? 1) there are no 4.7.rc2 modules. Should I use the ones for 4.7.x? 2) some modules are only available for 4.6.6, ie i18n module, shall I use cvs version? 3) what will happen to my site when 4.7 final is released? will I need to re-download and re-install all the modules and reconfigure them again? what about the ones from cvs? will they be be available in stable release? Or should I just wait until 4.7 final is released!
Thank you.
On 4/14/06, Salman Al-Rahma smhar@gawab.com wrote:
Steven Wittens wrote:
The second release candidate of Drupal 4.7 is now available.
I am thinking of upgrading my 4.6.6 drupal site to 4.7.rc2, but since I am using several modules.. I am wondering?
- there are no 4.7.rc2 modules. Should I use the ones for 4.7.x?
Depending on the module, yes.
- some modules are only available for 4.6.6, ie i18n module, shall I
use cvs version?
Again, it depends on the module. I don't know specifically about the i18n module. I recommend that you first decide if you have time to invest and possibly waste testing out the modules and upgrade path. If you do, then create a test site and try to follow the upgrade process to get your new site up. If it works, then you can repeat the process on your production server. If some modules don't work right or something else fails...you could try to figure out why and create patches until it does work and then everyone would really thank you!
- what will happen to my site when 4.7 final is released? will I need
to re-download and re-install all the modules and reconfigure them again? what about the ones from cvs? will they be be available in stable release?
It depends on a lot of things. When 4.7 final comes out it will _probably_ just be a simple upgrade, but it is likely that there will be small changes in core and in many modules in the next few weeks/months as modules get revisited, upgraded, and bug-fixed for a 4.7 compatible release, so that process of checking that you have the latest stable version could be tricky.
Or should I just wait until 4.7 final is released!
I guess I'll say it again: it depends :)
In my case, I've been dabbling with 4.7 and upgrading test sites sporadically with mixed results (some worked fine, others...not so much).
Regards, Greg
-- Growing Venture Solutions | Denver, CO Technology Solutions for Communities and Small Businesses http://growingventuresolutions.com/
-
Greg Knaddison - GVS -
Salman Al-Rahma -
Steven Wittens