diff mbox series

migration-guides: 5.3: mention barebox migration guides

Message ID 20251113085516.1067909-1-a.fatoum@pengutronix.de
State Under Review
Headers show
Series migration-guides: 5.3: mention barebox migration guides | expand

Commit Message

Ahmad Fatoum Nov. 13, 2025, 8:55 a.m. UTC
Inspired by the Yocto migration guides in this repository, I have been
maintaining release migration guides for barebox going back to
v2024.09.0, the first release after barebox was added to OE-core.

These contain actionable advice for users, e.g., rename of CONFIG options
or differences in the shell environment.

Reference the barebox migration guides from the Yocto migration guide
to help users with their updates.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Unsure about the placement; Are the release-notes a better place for this?
Or given that this would be a recurring aspect for future releases, just
add it once to the class documentation?
---
 documentation/migration-guides/migration-5.3.rst | 4 ++++
 1 file changed, 4 insertions(+)

Comments

Antonin Godard Nov. 13, 2025, 9:21 a.m. UTC | #1
Hi,

On Thu Nov 13, 2025 at 9:55 AM CET, Ahmad Fatoum wrote:
> Inspired by the Yocto migration guides in this repository, I have been
> maintaining release migration guides for barebox going back to
> v2024.09.0, the first release after barebox was added to OE-core.
>
> These contain actionable advice for users, e.g., rename of CONFIG options
> or differences in the shell environment.
>
> Reference the barebox migration guides from the Yocto migration guide
> to help users with their updates.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> Unsure about the placement; Are the release-notes a better place for this?

Given that your link points to a migration document, I think your link is well
placed under the misc changes, thanks. (Also, barebox's version shouldn't change
as we are close to feature freeze).

> Or given that this would be a recurring aspect for future releases, just
> add it once to the class documentation?

I would even just make the class description point to the barebox website:

"""
The :ref:`ref-classes-barebox` class manages building the `barebox
<https://barebox.org>`__ bootloader.
"""

Then a link to the doc / migration document at the end of the class description
could be a good idea too.

Thanks!
Antonin
diff mbox series

Patch

diff --git a/documentation/migration-guides/migration-5.3.rst b/documentation/migration-guides/migration-5.3.rst
index e59bc8c6389a..8ba9cb4f12b6 100644
--- a/documentation/migration-guides/migration-5.3.rst
+++ b/documentation/migration-guides/migration-5.3.rst
@@ -311,3 +311,7 @@  Miscellaneous changes
 
    Recipes currently using the ``fcntl-lock`` command should replace these by
    ``flock --fcntl``.
+
+- ``barebox`` has been updated from v2025.02.0 to v2025.09.0. Refer to the
+  `upstream migration guides <https://barebox.org/doc/latest/migration-guides/>`__
+  for migration advice.