Project

General

Profile

Feature #6551

Link to the known issues for current version from the general ones

Added by intrigeri almost 6 years ago. Updated over 1 year ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/29/2013
Due date:
% Done:

0%

Feature Branch:
Type of work:
Website
Blueprint:
Starter:
No
Affected tool:

Description

On https://tails.boum.org/support/troubleshooting/, we point to the long-standing known issues.

I've seen people (especially new users) on #tails who had no idea there were known issues specific to the last release, especially when (like just now) there is no link to the release notes in the News section of the web site homepage.

So, I suggest we add a link from the known issues page to the section about known issues on the last release notes. The release process will need to be updated to have a step to update this link (or, better, this should go into the general inc/ framework).


Related issues

Related to Tails - Bug #11665: Clean up known issues page, 4.0 edition Resolved
Related to Tails - Feature #15130: Restructure our support page and content Confirmed 09/28/2013

History

#1 Updated by u over 2 years ago

  • Assignee set to intrigeri
  • QA Check set to Info Needed

intrigeri wrote:

On https://tails.boum.org/support/troubleshooting/, we point to the long-standing known issues.

The link is now https://tails.boum.org/support/.

I've seen people (especially new users) on #tails who had no idea there were known issues specific to the last release, especially when (like just now) there is no link to the release notes in the News section of the web site homepage.

There are now links to the release notes in the News section, right?

So, I suggest we add a link from the known issues page to the section about known issues on the last release notes. The release process will need to be updated to have a step to update this link (or, better, this should go into the general inc/ framework).

While I still like this idea, it seems that there are no known issues in the release notes themselves. So either reformulate this ticket or close it please. Thanks!

#2 Updated by intrigeri over 2 years ago

  • Assignee changed from intrigeri to u

u wrote:

intrigeri wrote:

I've seen people (especially new users) on #tails who had no idea there were known issues specific to the last release, especially when (like just now) there is no link to the release notes in the News section of the web site homepage.

There are now links to the release notes in the News section, right?

Most of the time, yes, but not always. E.g. right now there is none: we have published 2+ blog posts since the last release.

So, I suggest we add a link from the known issues page to the section about known issues on the last release notes. The release process will need to be updated to have a step to update this link (or, better, this should go into the general inc/ framework).

While I still like this idea, it seems that there are no known issues in the release notes themselves.

https://tails.boum.org/news/version_3.0/#known-issues and https://tails.boum.org/news/version_2.12/ both have a "Known issues" section, so I don't understand. What do you mean with "there are no known issues in the release notes themselves"?

#3 Updated by BitingBird over 2 years ago

  • Related to Bug #11665: Clean up known issues page, 4.0 edition added

#4 Updated by sajolida almost 2 years ago

  • Related to Feature #15130: Restructure our support page and content added

#5 Updated by u almost 2 years ago

  • QA Check deleted (Info Needed)

I now better understand what BitingBird suggested: to add a link from the Known Issues page to each Tails version release note.

#6 Updated by u almost 2 years ago

  • Assignee deleted (u)

I don't volunteer to make this happen.

#7 Updated by u over 1 year ago

Could we automate this somehow, so that we don't have to modify the release process? Here is my idea: the latest version would always have a version/latest symlink and we can link from known issues to this symlink.

#8 Updated by intrigeri over 1 year ago

Could we automate this somehow, so that we don't have to modify the release process? Here is my idea: the latest version would always have a version/latest symlink and we can link from known issues to this symlink.

I don't think we can rely on webservers to follow filesystem symlinks (sysadmins often disable this for good reasons).

But I agree with the general idea! The closest thing we have to a symlink that would be automatically kept up-to-date is the inc/ framework I was referring to in the ticket description. E.g. just like wiki/src/inc/stable_amd64_iso_sig_url.html is automatically updated as part of the release process, we could have wiki/src/inc/stable_amd64_announce_url.html :)

Also available in: Atom PDF