diff mbox series

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

Message ID 20250407-b4-releases-notes-5-2-v1-1-76789ffce2f6@bootlin.com
State Under Review
Headers show
Series migration-guides/{migration,release-note}-5.2: update for 5.2 release | expand

Commit Message

Antonin Godard April 7, 2025, 8:59 a.m. UTC 
Document changes between 1c3020f17370 ("expat: Upgrade 2.7.0 -> 2.7.1")
up to e894acce6ede ("build-appliance-image: Update to master head
revision") in Poky:

- Add a note on the devtool upgrade-status change.
- Be more precise about the usage of multiple repositories in SRC_URI,
  mention that it makes sense for bare clones only.

As the walnascar branch has now frozen and is up for QA, these should be
the one of the last changes to these documents.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/migration-guides/migration-5.2.rst     | 16 +++++++++-------
 documentation/migration-guides/release-notes-5.2.rst |  4 ++++
 2 files changed, 13 insertions(+), 7 deletions(-)


---
base-commit: 3b50193fa0c9acf4a601aeae6e1c78d0e4a05aef
change-id: 20250407-b4-releases-notes-5-2-f3720cad4302

Best regards,
--
Antonin Godard <antonin.godard@bootlin.com>
diff mbox series

Patch

diff --git a/documentation/migration-guides/migration-5.2.rst b/documentation/migration-guides/migration-5.2.rst
index 4dd8cd20f..6b7d02d65 100644
--- a/documentation/migration-guides/migration-5.2.rst
+++ b/documentation/migration-guides/migration-5.2.rst
@@ -186,18 +186,20 @@  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"
+   SRC_URI = "git://some.host/somepath;bareclone=1;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.
+This was rarely used in the core repositories because it would only ever make
+sense for bare clones (the ``bareclone=1`` :term:`SRC_URI` option) where recipes
+take care of the Git checkout. This removal simplifies the code logic in several
+places.
 
-If one of your recipes is still using this mechanism, you can split the
-code source fetching into two separate entries::
+If one of your recipes is using this mechanism, you can split the code source
+fetching into two separate entries::
 
-   SRC_URI = "git://some.host/somepath;branch=branchX;name=nameX \
-              git://some.host/somepath;branch=branchY;name=nameY"
+   SRC_URI = "git://some.host/somepath;bareclone=1;branch=branchX;name=nameX \
+              git://some.host/somepath;bareclone=1;branch=branchY;name=nameY"
    SRCREV_nameX = "xxxxxxxxxxxxxxxxxxxx"
    SRCREV_nameY = "yyyyyyyyyyyyyyyyyyyy"
 
diff --git a/documentation/migration-guides/release-notes-5.2.rst b/documentation/migration-guides/release-notes-5.2.rst
index 2ad441449..ac9c6319a 100644
--- a/documentation/migration-guides/release-notes-5.2.rst
+++ b/documentation/migration-guides/release-notes-5.2.rst
@@ -447,6 +447,10 @@  New Features / Enhancements in |yocto-ver|
       with a matching hash and path, it will be linked, otherwise a new File
       element will be created.
 
+   -  The output of :ref:`devtool upgrade-status
+      <ref-manual/devtool-reference:Checking on the Upgrade Status of a Recipe>`
+      is now sorted by recipe name.
+
 -  Patchtest-related changes:
 
    -  Refactor pattern definitions in a ``patterns`` module.