Closed
Bug 20474
Opened 25 years ago
Closed 25 years ago
win32 verification build should pull by timestamp
Categories
(SeaMonkey :: Build Config, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: granrosebugs, Assigned: leaf)
Details
Just noticed this morning when I restarted the win32 build due to the
bustage that it wasn't pulling by timestamp. Would be good to have it pull by
timestamp so that we don't get horked by someone checking in during the pull.
I need to check that the unix and mac scripts are doing timestamp as well.
You shouldn't do that, because it makes pulling fixes later in the verification
process a royal pain in the ass.
When you check out by date/time stamp, it checks it out as a sticky tag. That
means that successive updates by using "cvs update" don't do anything because you
are frozen on that date/time.
In order to get fixes from the trunk into the tree, you have to issue a seperate
cvs update command, which is
"cvs update -A <file>" which clears the sticky tag and then updates the file.
You'd have to do this on each and every file that was checked in after the date
and time stamp. If you have a lot of fixes going into the tree, then you have to
issue all of these at the same time.
Additionally, we should be at the tip at all times. That's what we are verifying
for not only QA, but for engineers as well. This is why we beat people's heads in
when they check into a close tree.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Comment 2•25 years ago
|
||
forgot to clear this.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•