Closed Bug 466657 Opened 16 years ago Closed 16 years ago

commit message for ReleaseTaggingFactory should contain 'CLOSED TREE'

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

(Whiteboard: [hg-automation])

Attachments

(1 file)

Due to bug 458172 Tag was unable to complete because the tree was marked as 'CLOSED'. To make sure we don't hit this in the future we need to end our commit message with 'CLOSED TREE' - which will tell the hook on hg.m.o not to reject us.
Whiteboard: [hg-automation]
Assignee: nobody → bhearsum
I have nothing additional to say about this patch.
Attachment #350345 - Flags: review?(nthomas)
Summary: commit message for ReleaseTaggingFactory should be 'CLOSED TREE' → commit message for ReleaseTaggingFactory should contain 'CLOSED TREE'
Attachment #350345 - Flags: review?(nthomas) → review+
Comment on attachment 350345 [details] [diff] [review] make sure we can ignore the state of the tree when we branch and tag Checking in factory.py; /cvsroot/mozilla/tools/buildbotcustom/process/factory.py,v <-- factory.py new revision: 1.47; previous revision: 1.46 done
Attachment #350345 - Flags: checked‑in+
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: