Skip to content

Documentation update and prep. for v26.03.0#1460

Merged
troglobit merged 3 commits intomainfrom
releng
Mar 30, 2026
Merged

Documentation update and prep. for v26.03.0#1460
troglobit merged 3 commits intomainfrom
releng

Conversation

@troglobit
Copy link
Copy Markdown
Contributor

Description

Checklist

Tick relevant boxes, this PR is-a or has-a:

  • Bugfix
    • Regression tests
    • ChangeLog updates (for next release)
  • Feature
    • YANG model change => revision updated?
    • Regression tests added?
    • ChangeLog updates (for next release)
    • Documentation added?
  • Test changes
    • Checked in changed Readme.adoc (make test-spec)
    • Added new test to group Readme.adoc and yaml file
  • Code style update (formatting, renaming)
  • Refactoring (please detail in commit messages)
  • Build related changes
  • Documentation content changes
    • ChangeLog updated (for major changes)
  • Other (please describe): releng

Fixes #1456

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
When a YANG model change breaks existing startup configs, a migration
script must be included or devices in the field may be left unbootable
after upgrade.  Add a dedicated section explaining when scripts are
needed, where they live, and how they work.

Fixes #1459

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
[skip ci]

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
@troglobit troglobit requested a review from jovatn March 30, 2026 12:44
@troglobit troglobit enabled auto-merge March 30, 2026 13:25
Copy link
Copy Markdown
Contributor

@jovatn jovatn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!
Only question I have is if "Fix #1122 ..." should say "Fix #1454 ...", but I believe current text is intentional. Asking anyway.

@troglobit troglobit merged commit de3a44e into main Mar 30, 2026
@troglobit troglobit deleted the releng branch March 30, 2026 14:04
@troglobit
Copy link
Copy Markdown
Contributor Author

LGTM! Only question I have is if "Fix #1122 ..." should say "Fix #1454 ...", but I believe current text is intentional. Asking anyway.

Should probably have said both, at least in the Fixes line. But yeah, I this works too. Thanks for noticing, and thanks for the review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include reminder on adding 'migration script' in dev guide Add GitHub and Blog links to User Guide

2 participants