On 02/08/2012 06:32 AM, Alex Keybl wrote:
Can you clarify this? It sounds like changes would land on aurora *first*, and
then be forward-ported to mozilla-central. Which, IMO, goes against the basic
principles of how our branches work.
Only in the very rare instance where B2G v2 (Gecko changes in 18 and up) has
diverged too significantly to easily forward-port a patch, will we land
B2G-specific changes on FF17 only.
<snip>
I'm confused by this statement. Would this mean that certain features/fixes only
appear in 17? What about B2G v2 (and later)? Won't you *need* to port everything
anyhow, unless you want to be stuck on Gecko 17 until the end of days? :-)
Which brings me to another question: how long do you expect to keep B2G on Gecko
17? (eg. will v2 be off 17 or off the next ESR or off something else still?)
Fragmentation on eg. Android is well-documented, what's the plan in that
department? Will/would/could the partial update mechanism (or similar) be used
to just upgrade shipped phones to higher Gecko versions? Would those always be
ESRs? (I guess only the first question is really directly relevant to this
thread, but it seems to me the rest of the questions tie into it)
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
