Best upgrade strategy

[Glyn Millington]

"Andrew P." <infofarmer at mail.ru> writes:

> Glyn Millington wrote:
>> That is fine, but at the point when 5.4 becomes the production release, I
>> would like simply to track that for security fixes etc rather than follow
>> the stable developement branch.
>> Can I acheive that simply by putting
>> *default release=cvs tag=RELENG_5_4
>> into my cvsup file, at the right time -ie as soon as 5.4 becomes
>> a production release? ?  Or will there be such
>> complications that it would be best to perform yet another install (which
>> is smooth but slow on my set-up).
>
>
> Yes, you can use RELENG_5_4 tag to track
> security fixes when 5.4 is released. It
> goes smoothly most of the times, some
> people even managed to upgrade from
> 4.x to 5.x without reinstalling (ok,
> _that_ wasn't smooth). Just look through
> release notes, src/UPDATING and so on,
> and use mergemaster carefully.

Thanks Andrew - just needed to check this with those who know, to make
sure I had not miscontrued the Handbook!

atb

Glyn