1. 22 Mar, 2020 1 commit
  2. 26 Jan, 2020 1 commit
  3. 09 Jan, 2020 1 commit
  4. 05 Jan, 2020 1 commit
  5. 22 Dec, 2019 1 commit
  6. 03 Dec, 2019 2 commits
  7. 29 Nov, 2019 1 commit
  8. 27 Nov, 2019 1 commit
  9. 25 Nov, 2019 1 commit
  10. 22 Nov, 2019 1 commit
  11. 18 Nov, 2019 2 commits
  12. 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
  13. 08 Oct, 2019 1 commit
  14. 03 Oct, 2019 1 commit
  15. 28 Sep, 2019 2 commits
  16. 27 Sep, 2019 1 commit
  17. 25 Sep, 2019 1 commit
  18. 18 Sep, 2019 1 commit
  19. 06 Sep, 2019 1 commit
  20. 28 Aug, 2019 1 commit
  21. 10 Aug, 2019 1 commit
  22. 26 Jul, 2019 1 commit
  23. 11 Jul, 2019 2 commits
  24. 10 Jul, 2019 1 commit
  25. 09 Jul, 2019 1 commit
  26. 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
  27. 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
  28. 23 May, 2019 1 commit
  29. 17 Apr, 2019 2 commits
  30. 08 Apr, 2019 1 commit
    • intrigeri's avatar
      Make release notes writing instructions consistent with the implicit... · 31b7b34d
      intrigeri authored
      Make release notes writing instructions consistent with the implicit expectations of our release process doc (Closes: #16586)
      
      Our release process assumes that tech writers will push the release notes
      directly to the $WEBSITE_RELEASE_BRANCH (web/release-${TAG:?}) branch. But the
      tech writers doc told them to do something else. Let's resolve this conflict.
      31b7b34d
  31. 19 Mar, 2019 4 commits
  32. 21 Feb, 2019 1 commit