婆罗门
精华
|
战斗力 鹅
|
回帖 0
注册时间 2011-4-2
|
We will be producing two different sets of binaries for the Firefox 34 release. Firefox 34.0 will be given to all existing users, and Firefox 34.1 will be served from the website. We also need the ability to ship point releases to both of these sets of users. Ie:
* 34.0, 33.1 and earlier -> 34.0.1
* 34.1 -> 34.1.1
We will eventually merge the streams back together.
A bunch of us talked yesterday and came up with a few options:
1) Symlink mozilla-release to mozilla-release-34.1 on hg.mozilla.org, and create "mozilla-release-34.1" release configs. This was shot down because it would give us links to https://hg.mozilla.org/releases/mozilla-release-34.1 in the product.
2) Do 34.0 and 34.1 off of the "mozilla-release" release config. This was shot down because we couldn't build 34.0 and 34.1 simultaneously with this.
3) Create a fake "mozilla-release-34.1" branch in buildbot-configs/release configs that still ponits at "mozilla-release" on hg.m.o. This is the option we're pursuing at the moment. It should let us do 34.0 and 34.1 simultaneously without causing any in product differences to hg links.
nthomas started work on this in https://hg.mozilla.org/users/nth ... .1/rev/b78f0d6b1e55 and i've been continuing it in https://hg.mozilla.org/users/bhe ... /buildbot-configs/. We'd like to run staging releases to at least en-US build completion, but running them to full completion would be ideal. |
|
沪公网安备 31010702007642号 )
发表于 2014-12-1 18:23
