[EMAIL PROTECTED] wrote:
>
> Hi All!
>
> I scanned the archives and found nothing on
> this. I hope it's not a FAQ.
>
> I was wondering if anyone has added the ability
> to check out files based on the state of each
> CVS file in the repository. I manage a project
> with 5 developers, and when I do releases, it
> would be very cool to be able to check out the
> latest revision of state "release" of each file.
> The project is starting to get very complex -
> some files are ready for prime time, some
> aren't, etc...
>
> (Perhaps the functionality exists but I missed
> it?)
Now, if I'm reading you right, what you want to do is look
at CVS tagging.
What we do around here is this:
50 developers all humping around source code.
When a date is reached, a "tag" is created,
usually version and date, e.g. V10_01JAN2000...
cvs tag V10_01JAN2000
(Which should recursively tag the files that are in
the current and subdirectories, which are files in the
repository, with the tag V10_01JAN2000).
Now, even tho all the developers were SUPPOSED to be
done by a given date, and all their code tested
and whatnot, that never happens in the real world.
But the tag is made regardless, and then as developers
finish their work, they check in their files to the
branch ( whatever it may be ), then they "force" their
changes into the previously created tag.
cvs tag V10_01JAN2000 -F my_one_late_file.c
Now that file revision is part of that tag. Tada!
When everyone is finished and has their code in that tag,
the Release Guy checks out to the tag, does a build and releases
it.
Now, what you want to do is buy the Nickel Creek CD and listen
to The Lighthouse's Tale, or Ode to a Butterfly, which are both
FANTASTIC songs.
Rob
