Skip to content

content/breaking-changes: add breaking changes#1340

Open
vdawg-git wants to merge 1 commit intohyprwm:mainfrom
vdawg-git:add-breaking-changes
Open

content/breaking-changes: add breaking changes#1340
vdawg-git wants to merge 1 commit intohyprwm:mainfrom
vdawg-git:add-breaking-changes

Conversation

@vdawg-git
Copy link
Member

@vdawg-git vdawg-git commented Jan 5, 2026

Too many people had a hard time updating to 0.53. Lets make it a bit easier

@vdawg-git vdawg-git force-pushed the add-breaking-changes branch from f471a33 to 9c1e535 Compare January 5, 2026 10:53
@vdawg-git vdawg-git force-pushed the add-breaking-changes branch from 9c1e535 to 75f75e6 Compare January 5, 2026 13:08
@vaxerski
Copy link
Member

vaxerski commented Jan 5, 2026

why not just link to the tracker

@vdawg-git
Copy link
Member Author

So that others can contribute too. For example someone might have written a tool to automatically update the layer-rules. Or just some tips on how to re-create some deprecated niche behavior. You never know.

My idea is also that we automatically create a wiki PR when the breaking-tracker-issue gets a comment.

@Curious-Keeper
Copy link
Contributor

I am not disagreeing that people had issues updating, but of all the issues I saw it were 99% people not reading.
I migrated to 53, no issues, no breakage beyond what was clearly stated in the release notes as breaking, then fixed any issues using those docs. Anyone who made/makes a tool for the update, will be useless soon. no need to document it. IMO.

This sounds more like an expanded release note, not a wiki update.

@vdawg-git
Copy link
Member Author

vdawg-git commented Jan 11, 2026

The problem is that Hyprland now also has downstream consumers who provide a fully configured DE-experience.
That is awesome as it helps a lot of users to transition to the "Full-Linux"-experience (like PewdiePie), however that also means that they dont really know what is configured.
So just a small note in the release-notes will be a bit cryptic. Providing more elaborate instructions does definitely help.
Also we have no control over when someone updates. Maybe someone tries Linux, but doesnt use it, boots again after a couple of months and is greeted with a ton of config errors after updating.
Which also means that tools which help you to migrate like https://itsohen.github.io/hyprrulefix/ stay relevant for quite some timej (I just updated today for example).
Btw, Vaxry added this tool to the release notes. But imo he shouldnt have to do all that stuff by himself. Let the community help.

To end: Sure we could argue that it is ultimately the users fault for choosing something advanced like Hyprland, but we can also take a step back and view it from the above: People are migrating from Windows to Linux and we should support them.

@Curious-Keeper
Copy link
Contributor

In that view, I wouldn't disagree. I was once one of the windows to Linux users and if it weren't for exhaustive docs like Arch and Hyprland, I would have been a wreck.

I am all for tools, scripts, and docs to help users. Perhaps my comment was undue. I hope my remark was taken as helpful and not dismissive.

I also don't mind contributing.

@vdawg-git
Copy link
Member Author

All good, I should have elaborated more in the first place lol.
And awesome, thank you :)

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.

3 participants