Hi,
Talking about the CVS issue I would do the upgrade to SVN when the next release is out, make a release tag and switch to SVN to work on the next pre-release ;-).
You can say: Hei, the history is still on the CVS
See it like a book, there're volumes, I don't think there is a big problem to having a tag that says "Imported from CVS blablabla" as the first revision message for a SVN repository
The other topic on discussion, I would say: DOCUMENT. Yes, document it all, document what would be your decision and why. When someday you get blamed for a wrong decision he made because he didn't listened to what you said, then you have your documents. ;-)
But, if this work is limiting you, and you don't see a way in which your manager will change. Just leave.
Regards,
In reply to Re: CVS history woes
by fmerges
in thread CVS history woes
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |