460760 - hg release bundle doesn't apply, doesn't contain release tags

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Axel Hecht [:Pike]]

I just tried the release bundle for firefox 3.1 b1, and I found two issues:

First, the bundle doesn't apply, it doesn't contain the very first changeset. djc mentions hg bundle -a as a possible solution.

Secondly, the bundle doesn't contain the release tags, so within the repo that you get when applying the bundle on a repo with the initial changeset, you can't do an
hg up -r FIREFOX_3_1b1_RELEASE
which would probably be nice to have.

Comment 1

[Dirkjan Ochtman (:djc)]

Looks like the --all option to bundle appeared in 1.0. Before that, --base null should do the same thing.

Comment 2

[[e-mail] (:bhearsum)]

Attachment: [checked in] fix bundle by bundling from --null to the tip of the release branch

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 345092 [details] [diff] [review]
[checked in] fix bundle by bundling from --null to the tip of the release branch

r+. It kinda sucks we have to pull the tip of the relbranch just to get the tags, and that's only OK-ish because we only just tagged the the thing. hg handles .hgtags in a strange way :-S

Comment 4

[[e-mail] (:bhearsum)]

Comment on attachment 345092 [details] [diff] [review]
[checked in] fix bundle by bundling from --null to the tip of the release branch

Checking in factory.py;
/cvsroot/mozilla/tools/buildbotcustom/process/factory.py,v  <--  factory.py
new revision: 1.25; previous revision: 1.24
done