Background Updates/Implementation Strategies: Difference between revisions

Jump to navigation Jump to search
Line 53: Line 53:


  F(mozilla-release) < F(mozilla-aurora) < F(mozilla-beta) < F(mozilla-central)
  F(mozilla-release) < F(mozilla-aurora) < F(mozilla-beta) < F(mozilla-central)
[[User:LawrenceMandel|LawrenceMandel]] Is there a build id/timestamp? Is that a suitable identifier to use? Would this method break if FF moved off of hg?


Downsides of this approach:
Downsides of this approach:


* Updating between development branches might not work correctly.  For example, if we ever decide to move a bunch of users from the nightly update channel to the devtools update channel, the update process might fail to work because the devtools branch might have fewer chanegsets in the Mercurial repository.
* Updating between development branches might not work correctly.  For example, if we ever decide to move a bunch of users from the nightly update channel to the devtools update channel, the update process might fail to work because the devtools branch might have fewer chanegsets in the Mercurial repository.
[[User:LawrenceMandel|LawrenceMandel]] Perhaps we need to have a product specific preference included in the version. For example,  ffn.<hg generational index>.<hg full revision ID>, ffa.<hg generational index>.<hg full revision ID>,  ffb.<hg generational index>.<hg full revision ID>,  ff.<hg generational index>.<hg full revision ID>. In this way you can have different streams installed concurrently. Alternatively, if we already install different streams into different directories that approach can be expanded to support dev tools or other similar 'like' builds of FF.


=== Migration ===
=== Migration ===
Confirmed users
2,473

edits

Navigation menu