Release branch

[Raphael Collet]

Dear hackers,

Yesterday I created the branch "mozart-1-4-x" in the svn repository. 
This branch should be used for the maintenance of the releases 1.4.* of 
Mozart.  The releases themselves will be snapshots of that branch.

I order to avoid confusion and merge mess, I would like to establish a 
rule of thumb when updating both trunk and mozart-1-4-x:

	always merge from the trunk to the branch.

So when you introduce a bug fix, put it on the trunk first, test it, 
then merge that revision to the branch.  The rule is consistent with the 
fact that this is not a development branch.  And all the patches will be 
easier to track.


Thanks,
raph