|
|
|
|
Release Processes
|
|
|
|
|
=================
|
|
|
|
|
|
|
|
|
|
Project Release Cadence
|
|
|
|
|
-----------------------
|
|
|
|
|
|
|
|
|
|
The project currently aims to do a release once every 6 months which will be
|
|
|
|
|
tagged on the master branch. There will be a code freeze (stop merging
|
|
|
|
|
non-essential changes) up to 4 weeks prior to the target release date. The release
|
|
|
|
|
candidates will start appearing after this and only bug fixes or updates
|
|
|
|
|
required for the release will be merged. The maintainers are free to use their
|
|
|
|
|
judgement on what changes are essential for the release. A release branch may be
|
|
|
|
|
created after code freeze if there are significant changes that need merging onto
|
|
|
|
|
the integration branch during the merge window.
|
|
|
|
|
|
|
|
|
|
The release testing will be performed on release candidates and depending on
|
|
|
|
|
issues found, additional release candidates may be created to fix the issues.
|
|
|
|
|
|
|
|
|
|
::
|
|
|
|
|
|
|
|
|
|
|<----------6 months---------->|
|
|
|
|
|
|<---4 weeks--->| |<---4 weeks--->|
|
|
|
|
|
+-----------------------------------------------------------> time
|
|
|
|
|
| | | |
|
|
|
|
|
code freeze ver w.x code freeze ver y.z
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Upcoming Releases
|
|
|
|
|
~~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
|
|
These are the estimated dates for the upcoming release. These may change
|
|
|
|
|
depending on project requirement and partner feedback.
|
|
|
|
|
|
|
|
|
|
+-----------------+---------------------------+------------------------------+
|
|
|
|
|
| Release Version | Target Date | Expected Code Freeze |
|
|
|
|
|
+=================+===========================+==============================+
|
|
|
|
|
| v2.0 | 1st week of Oct '18 | 1st week of Sep '18 |
|
|
|
|
|
+-----------------+---------------------------+------------------------------+
|
|
|
|
|
| v2.1 | 5th week of Mar '19 | 1st week of Mar '19 |
|
|
|
|
|
+-----------------+---------------------------+------------------------------+
|
|
|
|
|
| v2.2 | 4th week of Oct '19 | 1st week of Oct '19 |
|
|
|
|
|
+-----------------+---------------------------+------------------------------+
|
|
|
|
|
| v2.3 | 4th week of Apr '20 | 1st week of Apr '20 |
|
|
|
|
|
+-----------------+---------------------------+------------------------------+
|
|
|
|
|
| v2.4 | 4th week of Oct '20 | 1st week of Oct '20 |
|
|
|
|
|
+-----------------+---------------------------+------------------------------+
|
|
|
|
|
|
|
|
|
|
Removal of Deprecated Interfaces
|
|
|
|
|
--------------------------------
|
|
|
|
|
|
doc: Convert internal links to RST format
Currently links between documents are using the format:
<path/to/><filename>.rst
This was required for services like GitHub because they render each
document in isolation - linking to another document is like linking
to any other file, just provide the full path.
However, with the new approach, the .rst files are only the raw
source for the documents. Once the documents have been rendered
the output is now in another format (HTML in our case) and so,
when linking to another document, the link must point to the
rendered version and not the .rst file.
The RST spec provides a few methods for linking between content.
The parent of this patch enabled the automatic creation of anchors
for document titles - we will use these anchors as the targets for
our links. Additional anchors can be added by hand if needed, on
section and sub-section titles, for example.
An example of this new format, for a document with the title
"Firmware Design" is :ref:`Firmware Design`.
One big advantage of this is that anchors are not dependent on
paths. We can then move documents around, even between directories,
without breaking any links between documents. Links will need to be
updated only if the title of a document changes.
Change-Id: I9e2340a61dd424cbd8fd1ecc2dc166f460d81703
Signed-off-by: Paul Beesley <paul.beesley@arm.com>
6 years ago
|
|
|
As mentioned in the :ref:`Platform Compatibility Policy`, this is a live
|
|
|
|
|
document cataloging all the deprecated interfaces in TF-A project and the
|
|
|
|
|
Release version after which it will be removed.
|
|
|
|
|
|
|
|
|
|
+--------------------------------+-------------+---------+---------------------------------------------------------+
|
|
|
|
|
| Interface | Deprecation | Removed | Comments |
|
|
|
|
|
| | Date | after | |
|
|
|
|
|
| | | Release | |
|
|
|
|
|
+================================+=============+=========+=========================================================+
|
|
|
|
|
| ``AARCH32``/``AARCH64`` macros | Oct '19 | v2.3 | Deprecated in favor of ``__aarch64__`` |
|
|
|
|
|
+--------------------------------+-------------+---------+---------------------------------------------------------+
|
|
|
|
|
| ``__ASSEMBLY__`` macro | Oct '19 | v2.3 | Deprecated in favor of ``__ASSEMBLER__`` |
|
|
|
|
|
+--------------------------------+-------------+---------+---------------------------------------------------------+
|
|
|
|
|
|
doc: Convert internal links to RST format
Currently links between documents are using the format:
<path/to/><filename>.rst
This was required for services like GitHub because they render each
document in isolation - linking to another document is like linking
to any other file, just provide the full path.
However, with the new approach, the .rst files are only the raw
source for the documents. Once the documents have been rendered
the output is now in another format (HTML in our case) and so,
when linking to another document, the link must point to the
rendered version and not the .rst file.
The RST spec provides a few methods for linking between content.
The parent of this patch enabled the automatic creation of anchors
for document titles - we will use these anchors as the targets for
our links. Additional anchors can be added by hand if needed, on
section and sub-section titles, for example.
An example of this new format, for a document with the title
"Firmware Design" is :ref:`Firmware Design`.
One big advantage of this is that anchors are not dependent on
paths. We can then move documents around, even between directories,
without breaking any links between documents. Links will need to be
updated only if the title of a document changes.
Change-Id: I9e2340a61dd424cbd8fd1ecc2dc166f460d81703
Signed-off-by: Paul Beesley <paul.beesley@arm.com>
6 years ago
|
|
|
--------------
|
|
|
|
|
|
|
|
|
|
*Copyright (c) 2018-2020, Arm Limited and Contributors. All rights reserved.*
|
