On 29/07/2013 19:43, Gregory Szorc wrote:
I'm proposing that we merge all the release repositories (central,
aurora, beta, release, esr, and b2g) into a single Mercurial repository.
The "default" branch/bookmark of this repository would be the equivalent
of mozilla-central. At train uplift time, we create a new branch (or
bookmark) called gecko-N (or similar) where N is the core gecko/platform
release version. If default/central is on 25, Aurora changes land in
gecko-24, Beta in gecko-23, etc. These could be supplemented with build
and release tags/branches as appropriate.
Now, maybe I'm wrong, but IIRC this is what we had before the rapid
release, and we switched away from that cause:
- people were pushing to the wrong head, basically everyday
- moving through heads requires more complex command than just moving
through local folders, you must recall the command and the branch name
- handling queue of patches for different branches is a nightmare, I
often have patches in queues for aurora, beta and central at the same time
- the more branches you have on a repository the slower it is, I don't
think this has ever been addressed, indeed I think we still need to
reset Try repository once in a while
- there were just too many branches, making very hard to find the one
you wanted from hg heads, try to find a head in the middle of hundreds
Imho, this will just generate confusion, I don't think data duplication
can be really considered an issue nowadays, roundtrips are fixable with
some really simple shell helper. Personally I don't see any advantage.
-m
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform