PUBLIC MARKS with tag migration

My (limited) experience is that folks tend to focus on moving the data between versions, and don't always think about the other ramifications involved in upgrading to a new major version of MySQL.

In general, you should do the following when upgrading from MySQL 4.0 to 4.1:

PHP5 est une vraie évolution du langage, rendant ce dernier plus sérieux et rigoureux. A condition de ne pas l'utiliser comme un vulgaire successeur de PHP4. En quelques points rapides, Jack D. Herrington vous expose ce qui pourrait bien changer votre façon d'aborder la POO en PHP : A PHP V5 migration guide.

Je vais peut-être revenir sur mon envie de passer au Mac...

Much of the data I’ve spent my life creating has been lost or seriously degraded through a series of proprietary formats and forced migrations

This article will walk you through the technical process of converting your CVS repository to Subversion--from deciding how much data to take with you, to prepping your data, to reviewing the most common options that you'll use in your conversion.

This page explains how I migrated the VideoLAN CVS repositories to Subversion while still allowing anonymous CVS access for users who did not want to move to Subversion. If you are a CVS user and have not yet fallen in love with Subversion, I suggest you have a look at this excellent project. In fact, I recommend to be familiar with Subversion before reading this document, because I may have missed important things.

Slides "migration to PHP 5.1" du php|tek 2006

Powerpoint de présentation du projet de migration du site Le Monde de JAVA vers PHP.

Today, started to test moving some of our PHP4 apps to PHP5.1.1. Some of this code was written for PHP 4.0.6, over 3 years ago. The migration so far has been relatively painless. Here are some of the problems we encountered.