Bug #17431

Consider dropping the latest release version and date from the website sidebar

Added by intrigeri 2020-01-12 19:40:33 . Updated 2020-05-05 11:41:51 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


One of the major pain points in our release process is the 2+ times when one waits for the full website to rebuild, due to the sidebar being updated with the release date & version bumps. Some of these waiting times are in the ~20 minutes order of magnitude, some are 1h or more.

Could we consider removing this information altogether?

This info was added to the sidebar almost 10 years ago via commit:0e3f9cf98278be787739f7293bc03a48efa75e8d.

sajolida told me there are big plans to change or remove the sidebar, as it currently is, in 2 months or so. I understand it’s about Feature #15112, as part of Feature #7627. It would be great if part of this work could benefit our RMs :)


Related issues

Related to Tails - Bug #17361: Streamline our release process Confirmed
Blocked by Tails - Feature #15112: Move our sidebar to the top Resolved


#1 Updated by intrigeri 2020-01-12 19:40:47

  • related to Bug #17361: Streamline our release process added

#2 Updated by sajolida 2020-01-17 12:06:21

  • Assignee set to sajolida
  • Target version set to Tails_4.3
  • Deliverable for set to 341

I’ll do this while working on Feature #16537 for Sponsor 1.

#3 Updated by anonym 2020-02-11 15:25:23

  • Target version changed from Tails_4.3 to Tails_4.4

#4 Updated by CyrilBrulebois 2020-03-12 09:55:42

  • Target version changed from Tails_4.4 to Tails_4.5

#5 Updated by sajolida 2020-03-12 18:41:45

  • Target version changed from Tails_4.5 to Tails_4.6

#6 Updated by sajolida 2020-03-20 22:27:49

  • Target version changed from Tails_4.6 to Tails_4.7

#7 Updated by sajolida 2020-04-17 20:20:17

  • Target version changed from Tails_4.7 to Tails_4.6

#8 Updated by sajolida 2020-05-01 16:01:09

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)

Done in Feature #15112 \o/

#9 Updated by sajolida 2020-05-04 17:54:11

#10 Updated by geb 2020-05-05 11:41:52

Hi !

I understand the reasons of this change (through never experienced it myself).

However, for an user point of view, I believe having this information easily accessible was something really useful & important. There have been lot of work done, or in progress to encourage people to use the last version, and to know if they do (example Feature #16796), thus I found a bit counter intuitive to not let people easily know if their images are up to date, when attending an install.

I know the information is accessible in other parts like the news ones, or by starting to follow the install process, just beleive it is less immediately accessible, and may end more people to need to immediately upgrade after the install, because they wont have easily found that their image is to not uptodate.

I don’t want to push for reconsidering it (thats a bit late..). However, I am afraid the drawbacks of this changes may have been underestimated and may ends to outcomes its advantages.. Curious to see if I will be the only one :).

EDIT: Would making this information available in the main/welcome page saves build time ? If so, it would be a good way to preserve this information (it doesnt have to be in the side/topbar), while preserving the benefits of this change.