migration-guides/{migration,release-note}-5.2: update for 5.2 release

Document changes between 0e91a1dabf ("adwaita-icon-theme: upgrade 47.0
-> 48.0") up to b3c21a23ad ("migration-guides/release-notes-5.2:
update for upcoming 5.2 release") in Poky.

(From yocto-docs rev: e61630ba2e4e865b57e920171a62824a4eba6533)

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

documentation/migration-guides/migration-5.2.rst

@@ -178,6 +178,32 @@ This should now be replaced by::
 
    UBOOT_ENTRYPOINT ?= "0x20008000"
 
+
+Git fetcher: support for multiple revisions per URL removed
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The support for having multiple Git revisions per URL in :term:`SRC_URI` was
+removed from BitBake, which means the following syntax is not supported
+anymore::
+
+   SRC_URI = "git://some.host/somepath;branch=branchX,branchY;name=nameX,nameY"
+   SRCREV_nameX = "xxxxxxxxxxxxxxxxxxxx"
+   SRCREV_nameY = "yyyyyyyyyyyyyyyyyyyy"
+
+This was rarely used in the core repositories, and this removal simplifies the
+code logic in several places.
+
+Git fetcher: Branch parameter now required in :term:`SRC_URI`
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The ``branch`` parameter is now required when specifying a Git repository in
+:term:`SRC_URI`, for example::
+
+   SRC_URI = "git://some.host/somepath;branch=branchX"
+
+A missing ``branch`` parameter used to produce a warning, and will now produce
+an error.
+
 Recipe changes
 ~~~~~~~~~~~~~~
 

documentation/migration-guides/release-notes-5.2.rst

@@ -43,6 +43,13 @@ New Features / Enhancements in |yocto-ver|
       This can be used for authentication of private NPM registries, among other
       uses.
 
+   -  The :term:`GRUB_MKIMAGE_OPTS` can be used to control the flags to the
+      ``grub-mkimage`` command in the context of the Grub recipe (``grub-efi``).
+
+   -  The :term:`SPDX_PACKAGE_VERSION` variable controls the package version as
+      seen in the SPDX 3.0 JSON output (``software_packageVersion``). The default
+      value for this variable is :term:`PV`.
+
 -  Kernel-related changes:
 
    -  :ref:`ref-classes-cml1`: in :ref:`ref-tasks-diffconfig`, do not override
@@ -81,6 +88,10 @@ New Features / Enhancements in |yocto-ver|
        -  ``qcom-x1e80100-lenovo-t14s-g6-adreno``
        -  ``qcom-x1e80100-lenovo-t14s-g6-audio``
        -  ``qcom-x1e80100-lenovo-t14s-g6-compute``
+       -  ``qcom-adreno-a623``
+       -  ``qcom-qcs8300-adreno``
+       -  ``qca-qca2066``
+       -  ``qcom-adreno-a2xx``
 
    -  ``linux-firmware``: split ``amgpu``, ``ath10k``, ``ath11k`` and ``ath12k``
       in separate packages.
@@ -208,6 +219,10 @@ New Features / Enhancements in |yocto-ver|
    -  ``rust-target-config``: Update the data layout for the *x86-64* target, as
       it was different in Rust from LLVM, which produced a data layout error.
 
+   -  The :term:`PACKAGECONFIG_CONFARGS` value if now passed to the ``cargo
+      build`` command, which means that Rust recipes can now properly define
+      their :term:`PACKAGECONFIG` configuration.
+
 -  Wic Image Creator changes:
 
    -  Allow the ``--exclude-path`` option to exclude symlinks.
@@ -330,6 +345,8 @@ New Features / Enhancements in |yocto-ver|
       -  ``wget``: increase timeout to 100s from 30s to match CDN worst
          response time.
 
+      -  ``wget``: Support setting :term:`PV` in :term:`SRC_URI`.
+
       -  Add support for fast initial shallow fetch. The fetcher will prefer an
          initial shallow clone, but will re-utilize an existing bare clone if
          there is one. If the remote server does not allow shallow fetches, the
@@ -494,6 +511,8 @@ New Features / Enhancements in |yocto-ver|
    -  ``systemd``: ``apparmor``, ``fido``, ``mountfsd``, ``nsresourced``
    -  ``ovmf``: ``debug``
    -  ``webkitgtk``: ``assertions``
+   -  ``iproute2``: ``iptables``
+   -  ``man-db``: ``col``
 
 -  Systemd related changes:
 
@@ -540,6 +559,9 @@ New Features / Enhancements in |yocto-ver|
    -  Add a sanity check to validate that the C++ toolchain is functional on the
       host.
 
+   -  Add a sanity check to check that the C++ compiler on the host supports
+      C++20.
+
    -  Add a sanity check to verify that :term:`TOPDIR` does not contain
       non-ASCII characters, as it may lead to unexpected build errors.