I assume there will an upgrade path from 4.6.5 to 4.7 stable when it's out, but wonder how complicated can it be? Would one say it's easier to deal with current bugs in 4.7-beta3 than install 4.6.5 with modules and then try to upgrade them to stable 4.7?

Comments

capmex’s picture

You can play with 4.7 betas, but they are not ready for production sites.

Something that can stop you from upgrading or developing a site on a certain version is the availability of modules.

Everytime a new beta is out I make a dump of my sites (running 4.6.5) and on my local machine I upgrade them to play with, fortunately a lot of contributed modules are already ported.
--
Webmaster Resources | Canadian Directory

Walt Esquivel’s picture

I'm looking into downloading XAMPP for Windows XP to my desktop in order to test my site under 4.7.0 beta 5 on a "local machine."

1. Are there better solutions and what do other folks use to test Drupal on a "local machine" running Windows XP if not XAMPP for Windows?

2. What are the advantages/disadvantages of using a "local machine" to test Drupal versus using a live web site? For an example of a disadvantage, I believe I read somewhere that email won't work on a "local machine" since it won't act as a mail server and thus can't send out emails??? An example of an advantage would be that one need not pay for a stand-alone hosted live web site and domain name simply to do testing when one can do it on a "local machine????

Thank you in advance for your kind assistance.

-----
Walt Esquivel, MBA, MA, Captain - U.S. Marine Corps (Veteran)
President, Wellness Corps, LLC
-----
Drupal Users and Developers by Geographical Location
http://drupal.org/node/46659

sepeck’s picture

XAMMP comes with a mailserver you can turn on. You can also download mailessentials if you feel the smtp server is important.

The biggest advantage is local test install and config to play with. You can test your backup and restore. You can reconfigure your site locally without risking your production site.

You can see that it's just not that big a deal where you run and test it and practice backup/restore in comfort.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Walt Esquivel’s picture

Hi Steven,

I've noticed your countless helpful replies to so many folks on the Drupal forum.

I for one would simply like to say "Thank you very much, Steven!" for all the kind and generous assistance you provide to so many people.

The Drupal community would not be the friendly, helpful, collaborative environment I've come to appreciate were it not for people such as you.

Have a great year! (A "day" seemed too short! ;) )

-----
Walt Esquivel, MBA, MA, Captain - U.S. Marine Corps (Veteran)
President, Wellness Corps, LLC
-----
Drupal Users and Developers by Geographical Location
http://drupal.org/node/46659

sepeck’s picture

Thanks, you too.

I posted some links in my blog about another more complex option VMWare and some caveats to be aware of with XAMMP on my blog

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Walt Esquivel’s picture

Helpful links & discussions on XAMPP & Drupal:

http://drupal.org/node/43330#comment-80514
http://drupal.org/node/43330#comment-80519
http://drupal.org/node/39745
http://drupal.org/node/45421#comment-98410
http://drupal.org/node/29581#comment-75442
http://drupal.org/node/29581#comment-93966

-----
Walt Esquivel, MBA, MA, Captain - U.S. Marine Corps (Veteran)
President, Wellness Corps, LLC
-----
Drupal Users and Developers by Geographical Location
http://drupal.org/node/46659

sepeck’s picture

Drupal core always always has an upgrade path. Here's a nice general guide in the handbook
http://drupal.org/upgrade/tutorial-introduction

Looks scary as hell doesn't it? It's not that bad and once you run through it a few times, it's merely a step by step process (on a test site) unless you have heavy customizations.

Drupal.org isn't on 4.7 codebase yet, so you decide. I haven't updated my sites either. So you're answer depends on what you are trying to setup and if you won't be hurt if there are issue's.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Dries’s picture

It is not advised to upgrade a production site yet.

It is advised that you (help) test the upgrade path in advance by using an exact copy of your production site.