File: release.rst

package info (click to toggle)
firefox 143.0.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,617,328 kB
  • sloc: cpp: 7,478,492; javascript: 6,417,157; ansic: 3,720,058; python: 1,396,372; xml: 627,523; asm: 438,677; java: 186,156; sh: 63,477; makefile: 19,171; objc: 13,059; perl: 12,983; yacc: 4,583; cs: 3,846; pascal: 3,405; lex: 1,720; ruby: 1,003; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 53; csh: 10
file content (31 lines) | stat: -rw-r--r-- 1,170 bytes parent folder | download | duplicates (12)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Release Selector
================

This command configures the tree in preparation for doing a staging release,
and pushes the result to try. The changes that that are made include:

- Updating the version number.
- Applying the migrations that are done as part of merge day.
- Disabling repacking most locales. (This can be disabled by passing ``--no-limit-locales``).

For staging a beta release, run the following (with an appropriate version number):

.. code-block:: shell

   $ mach try release --version 64.0b5 --migration main-to-beta

For staging a final release (rc or patch), run the following (with an appropriate version number)

.. code-block:: shell

   $ mach try release --version 64.0 --migration main-to-beta --migration beta-to-release

Once the decision task is on the push is complete, you can start the release
through `staging ship-it instance <https://shipit.staging.mozilla-releng.net/new>`_\ [#shipit]_.

.. note::

   If pushing from beta or release, the corresponding migration should not be
   passed, as they have already been applied.

.. [#shipit] This is only available to release engineering and release management (as of 2018-10-15).