Skip to content
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

distribution pages should link to most annoying bugs #255

Open
aspiers opened this issue Apr 23, 2018 · 3 comments
Open

distribution pages should link to most annoying bugs #255

aspiers opened this issue Apr 23, 2018 · 3 comments

Comments

@aspiers
Copy link
Member

aspiers commented Apr 23, 2018

[Originally filed in bsc#971397 (https://software.opensuse.org/ should link to most annoying bugs)]

Since https://software.opensuse.org/distributions/leap is linked to from https://www.opensuse.org/, it is the main page users will refer to when installing openSUSE Leap. Therefore it is important that any known bugs with the installation process are prominently accessible. However I found it quite hard (i.e. multiple hops) to navigate to this:

This seems to be confirmed by:

which shows that it's only linked from:

So one solution would be simply to fix openSUSE/landing-page#85 (need quick link to Leap portal) but even then the most annoying bugs page would be 3 clicks away from https://www.opensuse.org/#Leap and 4 clicks away from https://www.opensuse.org/. I really think we can do better than that. This raises the bigger question: do we need both https://software.opensuse.org/distributions/leap and https://en.opensuse.org/Portal:42.3 ? The former seems to be more focused on installation, so it would be the more logical place to link to most annoying bugs, but the link is currently within the latter.

@lnussel
Copy link
Member

lnussel commented Apr 23, 2018

the most annoying bugs list is mainly intended for the development phase. Anything affecting the distribution after the release should be documented in the release notes. So I think it would make sense to link those instead.

@aspiers
Copy link
Member Author

aspiers commented Apr 23, 2018

@lnussel Would (hopefully rare) annoying bugs discovered post-release be added to the release notes? If so I'm OK with that approach.

@lnussel
Copy link
Member

lnussel commented Apr 24, 2018

First I would hope that annoying bugs get fixed by means of maintenance update. If a problem cannot be fixed, eg when related to the installer then the release notes would be the right place to document them. Someone needs to have that in mind though and actually ask for a release notes entry.

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

No branches or pull requests

2 participants