- Update FSL layers names - Update Yocto Project Bugzilla url address - Add FSLC distros description
Signed-off-by: Fabio Berton <fabio.ber...@ossystems.com.br> --- release-notes/README | 4 ++-- release-notes/source/bsp-scope.rst | 24 ++++++++++++------------ release-notes/source/conf.py | 6 +++--- release-notes/source/distros.inc | 4 ++++ release-notes/source/introduction.rst | 7 ++++--- release-notes/source/known-issues.rst | 4 ++-- release-notes/source/source-code.rst | 9 +++++++++ release-notes/source/test-results.rst | 2 +- release-notes/source/variables.inc | 2 +- 9 files changed, 38 insertions(+), 24 deletions(-) create mode 100644 release-notes/source/distros.inc diff --git a/release-notes/README b/release-notes/README index e1b7c9e..9665ea3 100644 --- a/release-notes/README +++ b/release-notes/README @@ -37,8 +37,8 @@ Here's an example: $ ./bitbake-metadata2doc.sh ~/src/fsl-community-bsp ~/src/gitdm 1.5 1.6 By default, bitbake-metadata2doc.sh collects data out of bitbake's -metadata for all machines it can find in the meta-fsl-arm and -meta-fsl-arm-extra layers. You can restrict the machines to collect +metadata for all machines it can find in the meta-freescale and +meta-freescale-3erparty. You can restrict the machines to collect data from by setting the MACHINES variable in your environment. bitbake-metadata2doc.sh will write its output to release-note's `source' diff --git a/release-notes/source/bsp-scope.rst b/release-notes/source/bsp-scope.rst index f0f0f74..97ca49d 100644 --- a/release-notes/source/bsp-scope.rst +++ b/release-notes/source/bsp-scope.rst @@ -4,14 +4,14 @@ *********************** The scope of the |project_name| includes the meta layers: - * `meta-fsl-arm <http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/?h=krogoth>`_: - provides the base support and Freescale ARM reference boards; - * `meta-fsl-arm-extra <https://github.com/Freescale/meta-fsl-arm-extra/tree/krogoth>`_: + * `meta-freescale <http://git.yoctoproject.org/cgit/cgit.cgi/meta-freescale/?h=morty>`_: + provides the base support and Freescale ARM and PPC reference boards; + * `meta-freescale-3rdparty <https://github.com/Freescale/meta-freescale-3rdparty/tree/morty>`_: provides support for 3rd party and partner boards; - * `meta-fsl-demos <https://github.com/Freescale/meta-fsl-demos/tree/krogoth>`_: - provides images recipes, demo recipes, and packagegroups used to easy the - development with Yocto Project. - * `Documentation <https://github.com/Freescale/Documentation/tree/krogoth>`_: + * `meta-freescale-distro <https://github.com/Freescale/meta-freescale-distro/tree/morty>`_: + provides distros support, images recipes, demo recipes, and packagegroups + used to easy the development with Yocto Project. + * `Documentation <https://github.com/Freescale/Documentation/tree/morty>`_: provides the source code for |project_name| Release Notes (RN), User Guide (UG) and Frequently Asked Questions (FAQ) @@ -36,8 +36,8 @@ regular open source licenses (GPLv2 for example). The close sourced packages are released under the Freescale License (known as EULA). Each package has a copy of EULA inside itself and a copy of the EULA text -is also included inside **meta-fsl-arm** root dir -(``sources/meta-fsl-arm/EULA``). +is also included inside **meta-freescale** root dir +(``sources/meta-freescale/EULA``). The |project_name| handles the EULA acceptance by prompting user to read and accept EULA text at the very first environment setup. It is user's duty to read @@ -107,8 +107,8 @@ Machine Maintainers ------------------- Since |project_name| Release 1.6 (Daisy), the maintainer field in machine -configuration files of **meta-fsl-arm** and **meta-fsl-arm-extra** is mandatory -for any new board to be added. +configuration files of **meta-freescale** and **meta-freescale-3rdparty** +is mandatory for any new board to be added. So now on, every new board must have someone assigned as maintainer. This ensures, in long term, all boards with a maintainer assigned. @@ -124,7 +124,7 @@ The maintainer duties: * Keep the most usual images building and booting When a build error is detected, the maintainer will "fix" it. For those -maintainers with kernel control (meta-fsl-arm-extra), it is expected that they +maintainers with kernel control (meta-freescale-3rdparty), it is expected that they properly fix the kernel issue (when it's a kernel issue). However, anything out of community control should be worked around anyway. diff --git a/release-notes/source/conf.py b/release-notes/source/conf.py index 0ea97f1..55ddfea 100644 --- a/release-notes/source/conf.py +++ b/release-notes/source/conf.py @@ -51,9 +51,9 @@ copyright = u'2013-2016, FSL Community BSP Team' # built documents. # # The short X.Y version or version name if applicable. -version = 'krogoth' +version = 'morty' # The full version, including alpha/beta/rc tags. -release = '2.1' +release = '2.2' if tags.has('draft'): release = release + " (Draft document)" @@ -269,7 +269,7 @@ texinfo_documents = [ epub_title = u'FSL Community BSP Release Notes' epub_author = u'FSL Community BSP Team' epub_publisher = u'FSL Community BSP Team' -epub_copyright = u'2013, FSL Community BSP Team' +epub_copyright = u'2013-2016, FSL Community BSP Team' # The language of the text. It defaults to the language option # or en if the language is not set. diff --git a/release-notes/source/distros.inc b/release-notes/source/distros.inc new file mode 100644 index 0000000..22bee1b --- /dev/null +++ b/release-notes/source/distros.inc @@ -0,0 +1,4 @@ +* **fslc-framebuffer**: Distro for Framebuffer graphical backend. This distro doesn't include x11 and wayland features. +* **fslc-wayland**: Distro for Wayland without X11. This distro include wayland feature but doesn't has x11 support. +* **fslc-x11**: Distro for X11 without wayland. This distro include x11 feature and doesn' has wayland support. +* **fslc-xwayland**: Distro for Wayland with X11. This distro include both wayland and x11 features. diff --git a/release-notes/source/introduction.rst b/release-notes/source/introduction.rst index bb62b4f..4cb759a 100644 --- a/release-notes/source/introduction.rst +++ b/release-notes/source/introduction.rst @@ -132,8 +132,9 @@ In addition to the normal Yocto Project upstream process, there is also a BSP up The BSP upstream cycle starts just after a |freescale_release_name| is published in `git.freescale.com <http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git/>`_. The patches to adapt the recipes from **meta-fsl-bsp-release** are sent out for review -to the **meta-freescale** mailing list and are merged in the **meta-fsl-arm** and -**meta-fsl-demos** layers or upstreamed to Yocto Project accordingly. +to the **meta-freescale** mailing list and are merged in the **meta-freescale**, +**meta-freescale-3rdparty** or **meta-freescale-distro** layers or upstreamed +to Yocto Project accordingly. A more detailed step-by-step process is shown below: @@ -172,7 +173,7 @@ layer. Therefore, the release does not receive updates and bug fixes. The |project_name| is a reference system that can be used as a base for products and is an open project that accepts contributions from the community. It supports a wide range of boards which range from Freescale evaluation boards -(**meta-fsl-arm** layer) to third-party boards (**meta-fsl-arm-extra**). +(**meta-freescale** layer) to third-party boards (**meta-freescale-3rdparty**). The release is a "*moving target*”, so there are updates on top of the released source code, such as the addition of new features and bug fixes. diff --git a/release-notes/source/known-issues.rst b/release-notes/source/known-issues.rst index 71e71ed..0d34019 100644 --- a/release-notes/source/known-issues.rst +++ b/release-notes/source/known-issues.rst @@ -40,7 +40,7 @@ Known Issues Open ---- In order to see the current bug list, please use following URL: - https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-fsl-arm + https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-freescale .. table:: List of open bugs @@ -60,7 +60,7 @@ Known Issues The list of known issues for the |project_name| can be seen at the following URL: - https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-fsl-arm + https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-freescale It has not been included here as it changes every time bug fixes are included during the maintenance cycle of the release and it would diff --git a/release-notes/source/source-code.rst b/release-notes/source/source-code.rst index 3ffee2a..9cf608b 100644 --- a/release-notes/source/source-code.rst +++ b/release-notes/source/source-code.rst @@ -151,3 +151,12 @@ Project's reference images in `Yocto Project Reference Manual <http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-images>`_ .. include:: images.inc + +Distros +------- + +The following distros are supported by |project_name|. + +.. include:: distros.inc + +*NOTE: Poky's distros are still available to use.* diff --git a/release-notes/source/test-results.rst b/release-notes/source/test-results.rst index d8cebc2..33fe359 100644 --- a/release-notes/source/test-results.rst +++ b/release-notes/source/test-results.rst @@ -9,5 +9,5 @@ The results and known issues, from Linux Kernel, GPU and VPU packages can be found in the Freescale Release Notes (Download tab of freescale.com/imx). -For boards from meta-fsl-arm-extra, the test cycle is performed by +For boards from meta-freescale-3rdparty, the test cycle is performed by each mantainer. diff --git a/release-notes/source/variables.inc b/release-notes/source/variables.inc index 0815891..82fb9bc 100644 --- a/release-notes/source/variables.inc +++ b/release-notes/source/variables.inc @@ -1,3 +1,3 @@ -.. |release_name| replace:: Krogoth +.. |release_name| replace:: Morty .. |project_name| replace:: FSL Community BSP .. |freescale_release_name| replace:: Freescale Official Release -- 2.1.4 -- _______________________________________________ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale