1. 17 Nov, 2020 2 commits
  2. 10 Nov, 2020 1 commit
  3. 20 Oct, 2020 1 commit
  4. 19 Oct, 2020 1 commit
  5. 25 Aug, 2020 1 commit
  6. 29 Jul, 2020 1 commit
  7. 28 Jul, 2020 4 commits
  8. 30 Jun, 2020 1 commit
  9. 07 Apr, 2020 1 commit
  10. 23 Mar, 2020 1 commit
  11. 11 Mar, 2020 2 commits
  12. 09 Jan, 2020 1 commit
  13. 22 Dec, 2019 1 commit
  14. 03 Dec, 2019 1 commit
  15. 11 Oct, 2019 1 commit
    • sajolida's avatar
      Redirect /upgrade to /doc/upgrade#manual · cf41804a
      sajolida authored
      - We've had 2 places to document manual upgrades since 2016,
        /doc/upgrade then pointing to /upgrade for the actual meat. Having a
        single place prevents people to jump around needlessly.
      
      - Tails Upgrader has been pointing to /doc/upgrade since 2014 and these
        old versions of Tails will continue to point to it.
      
      - We could as well redirect /doc/upgrade/#manual to /upgrade but
        /doc/upgrade has the advantage of putting both techniques in
        perspective.
      
      - /doc/upgrade (formerly /doc/first_steps/upgrade) is very well indexed
        by search engines while we prevented /upgrade to be indexed by
        'noindex'.
      cf41804a
  16. 27 Sep, 2019 1 commit
  17. 11 Jul, 2019 2 commits
  18. 23 Jun, 2019 1 commit
    • sajolida's avatar
      Improve top-level heading · f449ddb1
      sajolida authored
      "Changes" has a probably stronger meaning as the first word in the title
      when put in parallel with "[New] features" and "[Fixed] problems".
      Upgrades are one type of changes.
      f449ddb1
  19. 20 Jun, 2019 1 commit
    • sajolida's avatar
      Remove 1 depth of heading · f8ebf359
      sajolida authored
      This "Change" section doesn't bring much and look especially weird in
      short release notes.
      f8ebf359
  20. 19 Mar, 2019 4 commits
  21. 21 Feb, 2019 1 commit
  22. 13 Feb, 2019 3 commits
  23. 29 Jan, 2019 1 commit
  24. 03 Oct, 2018 5 commits
  25. 04 Sep, 2018 1 commit