removing CVS in Handbook Updating and Upgrading chapter

[Warren Block]

On Sun, 27 Jan 2013, Isaac (.ike) Levy wrote:

>>> + ports, cvsup access end-of-lifed Feb 28
> - great- drop all ports references to cvs/cvsup
>
>>> - source, cvsup deprecated - no end-of-life date set
> - please do not drop the current canonical base/src fetch method from the handbook!
>
> However, cvsup is still merely deprecated, without a clear canonical replacement, (per notes in my previous email).

Understood, but really that is an argument against deprecating CVS, not 
removing it from the docs.

> Therefore, I hope I'm being clearly understood that it's cleaner for *users* to still fetch *base/src* with cvsup, until:
>
>  - canonical src fetch replacement is in place
>  - whenever cvsup for base/src has an end-of-life date set, (like ports does- Feb. 28!)
>
> At that point, it seems rational that the last references to cvsup can disappear.  (The rest of CVS can disappear before that though?)

Say we leave CVS references in this chapter, and CVS for source goes 
away in (for example) six months.  Anyone who starts using CVS in that 
time will be forced to switch.  And they would be justifiably upset, 
because they were offered an option that was going away.

My personal feeling is that continuing to suggest CVS for -STABLE or 
-CURRENT, even with a deprecation warning, is a disservice to those 
users.

Using CVS is still documented in Appendix A, along with a big 
deprecation warning.