CVS Tags to mark releases, even release candidates

For feature requests and bug reports RC15 RC16. Please use the forum at http://forum.ultravnc.net/

Hi!

I am working on a slightly modified version of the VNC server, to adjust
it to our needs. Therefore, I need to work on the source code, rather
than used compiled versions.
Every time a new release (or release candidate) is made, I need to
update the source to the latest revision, as I will want my code to
include all fixes made. A good way to achieve that is to simply get the
source from CVS, edit the files locally according to my needs, and do
updates as appropriate. With a little bit of chance, and since my
changes are pretty limited, this process merges & the new changes, and I
do not need to do much to get everything updated.
However, I do not believe that tags are created every time a release is
created (at least, not for release candidates), which makes it hard for
me to get the exact source code of a specific release merged with my
changes. This exposes me to getting possibly broken states to the source
tree (with partial commits for instance), rather than getting exact code
of a release.

Would you guys consider creating a CVS tag for each release (including
release candidates)? I believe this would help people in my situation a
great deal, and I am sure others as well, while hopefully not requiring
a lot of effort.

Thanks,
-georges


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click