Just a thought… Perhaps the “known issues” section might benefit from a bit of pruning? I’m not sure that having them go back nearly a year is of any benefit; too many old ones could be confusing (especially for anyone relatively new round here).
5 Likes
I’m tempted to agree.
However, there are extreme cases where a User hasn’t updated a system in an awfully long time, or has opted to install using a very old Manjaro Installer ISO they had laying around.
Neither of these scenarios are ideal, but some of those solutions listed might be crucial to allowing a continued update path.
3 Likes
I’m not all that sure about “extreme”. Been seeing that a lot here! Or, probably more to the point … not properly maintained 
3 Likes
“known issues” section might benefit from a bit of pruning?
How about if every time a “known issue” is created for an update post, it gets copied to a permanent “Past Known Issues” post. It wouldn’t need to be very prominent as long as it was searchable.
Then keep only the previous two or three in the update post and have a link to the permanent post for older ones.
I imagine that would make it even less likely that newer Users would actually read it. Nonetheless, thanks for your comment.
You are wecome to open a new thread under Feedback if you would like to share further opinions on this.
Regards.
2 Likes
Good suggestion, it’s appreciated. But in a similar vein to @soundofthunder’s post above, we do have something similar in place, i.e. can split posts off to new topics which are then more easily searchable separately from the main update threads. That way at least they aren’t necessarily tied to a specific update thread.
While I agree its a tad too embiggined right now, and while I know a user can always consult a previous upgrade announcement…
I am still hesitant to trim more than ‘up to 12 months’.
But I also think we could have another break, with the simplified/shortened versions that pertain under an ‘older than 3 months’, just as it is with ‘older than 6 months’.
We could also do with lowering the volume on the ‘linux610 is EOL’, and probably be mindful about not breaking up the formatting so dramatically in the future.
2 Likes
Welp. I went ahead and converted the ‘6 months’ to ‘100 days’.
( Thats 3 months plus some change )
Also did a bit of cleaning up and fixing of some previously incorrectly nested notes, toned down the EOL notices, etc.
I think its a nice compromise on retaking some real estate while keeping the same amount of info.
But it can always be reverted if its disliked.
3 Likes