content/breaking-changes: add breaking changes#1340
content/breaking-changes: add breaking changes#1340vdawg-git wants to merge 1 commit intohyprwm:mainfrom
Conversation
f471a33 to
9c1e535
Compare
9c1e535 to
75f75e6
Compare
|
why not just link to the tracker |
|
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. |
|
I am not disagreeing that people had issues updating, but of all the issues I saw it were 99% people not reading. This sounds more like an expanded release note, not a wiki update. |
|
The problem is that Hyprland now also has downstream consumers who provide a fully configured DE-experience. 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. |
|
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. |
|
All good, I should have elaborated more in the first place lol. |
Too many people had a hard time updating to
0.53. Lets make it a bit easier