-
-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration guide from v 2.x.x to 3.x.x Breaking changes link is broken #1339
Labels
Comments
There's an older revision of that wiki that still shows them. |
Better late than never, this is fixed now. 🙂 |
wborn
added a commit
to wborn/openhab-docs
that referenced
this issue
Jul 31, 2023
These breaking changes were added to the OH3 release notes again recently (openhab/openhab-distro#1339). Signed-off-by: Wouter Born <github@maindrain.net>
wborn
added a commit
to wborn/openhab-docs
that referenced
this issue
Aug 4, 2023
These breaking changes were added to the OH3 release notes again recently (openhab/openhab-distro#1339). Signed-off-by: Wouter Born <github@maindrain.net>
stefan-hoehn
pushed a commit
to openhab/openhab-docs
that referenced
this issue
Aug 7, 2023
These breaking changes were added to the OH3 release notes again recently (openhab/openhab-distro#1339). Signed-off-by: Wouter Born <github@maindrain.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Official docs https://www.openhab.org/docs/configuration/migration/ guides the user to the wiki page "Breaking Changes in openHAB 3" (https://github.com/openhab/openhab-distro/wiki/Breaking-Changes-in-openHAB-3), which in turn
guides the user to another document (https://github.com/openhab/openhab-distro/releases/tag/3.0.0#breaking-changes-that-require-manual-interaction-after-the-upgrade).
It has a quick link "Breaking Changes" which refers the document that does not exist: https://github.com/openhab/openhab-distro/blob/3.0.0/breaking-changes-that-require-manual-interaction-after-the-upgrade.
As a result there is no way to see the breaking changes when migrating from v2.x.x to v3.x.x
The text was updated successfully, but these errors were encountered: