Always read post 2 for potential issues and solutions

[nikgnomic]

Am I to understand that this was not in place until six hours after 24.0 reached GA? That being the case, I was unaware of it

Everyone missed some of the things, but the important things were sorted out by someone
and anyone can read the history and consider how to avoid or mitigate update problems in the future

Wiki edits usually have a related post in the topic. The top dudes for the May massive update are:

• Plasma 6 update via TTY - #84 by 1efaf7d71a8637c6800a

• plasma-firewall - #273 by CarlLaFong

• I added issue for Xfce Qt themes from comment by #166 by Teo

As far as I could see at the time, comments prior to wiki edits were reporting a lack of information to read in post 2. But I was on the lookout for non-KDE issues and off-topic stuff to move out of the dogpile

delay the release until supporting documentation is in place.

There was a gitlab page showing the release blockers. Maybe that could include items for documentation and implementation linked up to “known issues” in Testing

@wongs

It was clear from the past few months of Plasma testing that widgets, themes etc might cause issues if not reverted

Manjaro Team and community did excellent work on the packages, but deployment of the update to stable branch was lacking warnings and information

@Kobold

I saw at least from my 5 visits that Know Issues in Testing Branch wasn’t in sync with Known Issues Stable Branch.

I posted to Testing branch wiki last year and information was copied across to Stable branch no problem. But this year I had to copy 2 or 3 posts from Testing to Stable. This is not optimal for users if I am not on the forum for a day or 2 to check update announcement

@cscs

since users found out that depending on their trust level they can add to that known issues post … so some do. And regardless of the quality of those additions … they rarely follow it up with also applying it to the other thread(s).

user wiki content seems to be good for quality

No comment about moderators. They should be doing their own introspection

---

I recall a couple of times since 2016 when PhilM “strongly recommended” all users to log out and update from TTY, but I don’t recall this being needed for only one DE before
This should be considered ahead of time and posted on time to stable branch

.pacnew files should be notified automatically, with specific merge instructions decided for each case if needed

And we should be spamming everywhere with messages to read the update announcement if another massive one is expected