[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Don't commit during tagging
RE: Don't commit during tagging
Sun, 03 Jul 2005 13:26:29 -0700
Needn't worry about that. CVS tags the matching copies of the revisions in
your working folder only. In other words, if you just did a checkout of
-foo.bar (rev 1.6) and a developer shortly after, committed a new rev 1.7,
your build and compile are based on 1.6 and when you tag
cvs/respository/project...you have only tagged rev 1.6 (e.g.
release_build_1.2.139) and 1.7 is not of your concern. And when you do a
checkout base on release_build_1.2.139 in the future, you'd always get rev
1.6 of -foo.bar.
To ensure proper tagging I always work with a clean & fresh working folder.
Delete your local project and do a fresh checkout. You can now tag this
pristine working folder, however, if your build does not compile or the
Mainline's in a broken state (it does happen, you know?), then you've just
wasted a tag.
I always tag after, only because I have to modify couple of files and commit
them during or after the build. Historically most folks or build/release
engineers tag after they've made sure they have a clean build. But everyone
does it differently based on their needs.
AlwaysSo it doesn't matter whether you t
----Original Message Follows----
From: "Stephan Lange" <address@hidden>
Subject: Don't commit during tagging
Date: Sun, 3 Jul 2005 20:25:03 +0200
Received: from lists.gnu.org ([188.8.131.52]) by mc7-f34.hotmail.com with
Microsoft SMTPSVC(6.0.3790.211); Sun, 3 Jul 2005 11:30:45 -0700
Received: from localhost ([127.0.0.1] helo=lists.gnu.org)by lists.gnu.org
with esmtp (Exim 4.43)id 1Dp9G1-0007Um-H2for address@hidden; Sun, 03 Jul
2005 14:31:57 -0400
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)id
1Dp9Ey-0007L8-OHfor address@hidden; Sun, 03 Jul 2005 14:30:53 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)id
1Dp9Ev-0007Jt-HKfor address@hidden; Sun, 03 Jul 2005 14:30:51 -0400
Received: from [184.108.40.206] (helo=monty-python.gnu.org)by lists.gnu.org
with esmtp (Exim 4.43) id 1Dp9Ev-0007IV-Bafor address@hidden; Sun, 03 Jul
2005 14:30:49 -0400
Received: from [220.127.116.11] (helo=mail.gmx.net)by monty-python.gnu.org
with smtp (Exim 4.34) id 1Dp9Fw-0000yu-69for address@hidden; Sun, 03 Jul
2005 14:31:52 -0400
Received: (qmail invoked by alias); 03 Jul 2005 18:26:02 -0000
Received: from e180009081.adsl.alicedsl.de (EHLO mmadmin) [18.104.22.168]by
mail.gmx.net (mp019) with SMTP; 03 Jul 2005 20:26:02 +0200
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2149
List-Id: Announcements and discussions for the CVS version control
X-OriginalArrivalTime: 03 Jul 2005 18:30:45.0421 (UTC)
We are using cvs in an enterprise web-application development project.
My task is the build and deployment of the new releases.
The build will be making every week. Before I start the process I tag all
the modules I need and then check out the modules with this tag.
The tagging process needs time because some modules are very big.
The question is, how can I be sure that during my tagging operation, no
developer is committing some new stuff to the modules?
Thanks for your help!
Info-cvs mailing list