I check out files from CVS server. Then I made some changes in local file, I commit it. So the local and remote file are updated.
But problem is ,say a file is "Base.java 1.1" in local. After commit and update, the file name will be "Base.java 1.2". I don't want to update the version number ("1.1"), because I just made some little changes.
I think you're confusing your version numbering with CVS's version numbering. Every time you check in something to CVS, its version number gets bumped. The CVS version ID is, if you will, the "primary key" (along with the file path/name) that allows retrieval of the file as of that update time, so it must always be unique, and CVS's numbering scheme ensures that it will be so.
Unfortunately, when you want to create a distributable release of your project, CVS has no scheme to support that. And, bear in mind that due to the fact that usually some parts of the system will be checked in with updates more than others, your "release 1.2" may actually contain an index.jsp v1.1, web.xml v1.4, struts-config.xml v1.4 and MyAction.java v1.2.
The way around this is to use CVS tags. Unfortunately, CVS doesn't permit a tag to be named "1.2", so you have to be creative and tag files something like "V1_2" instead.
Customer surveys are for companies who didn't pay proper attention to begin with.