1. 05 Nov, 2020 8 commits
  2. 20 Oct, 2020 1 commit
  3. 22 Sep, 2020 1 commit
  4. 30 Jul, 2020 1 commit
  5. 25 May, 2020 1 commit
  6. 01 Apr, 2020 1 commit
  7. 24 Mar, 2020 1 commit
    • Cyril 'kibi' Brulebois's avatar
      Catch up with origin's destination branch. · f7970ac6
      Cyril 'kibi' Brulebois authored
      The release manager might have made sure their release checkout has an
      updated release branch (e.g. stable) when starting the release process,
      but other local branches might be lagging behind.
      To make possible conflicts easier to spot/solve, ensure one catches up
      with the destination branch on the remote before trying to merge the
      source branch into it.
  8. 10 Oct, 2019 1 commit
    • intrigeri's avatar
      Drop obsolete reference to feature/jessie. · 23c73a45
      intrigeri authored
      Besides, during the Tails/Buster development cycle, we've treated
      feature/buster as an overlay on top of devel, instead of as a main branch,
      so this part of the instructions don't fit anyway.
  9. 05 Aug, 2019 1 commit
    • intrigeri's avatar
      Consistently suggest forking us on Salsa. · 68a08803
      intrigeri authored
      In the past we recommended forking us on gitlab.com, which was the only mirror
      of our main Git repository (aka. tails.git) with a user-friendly "Fork" feature.
      Since then, we have another such mirror — Salsa — that we actively use and keep
      track of: for example, merge requests can be submitted there and the Foundations
      Team will review them. This increases the chances that other teams start to do
      the same there as well, until we've decided which GitLab instance will become
      the canonical location for our code in the future.
      This contrasts with gitlab.com, where we have disabled MRs on purpose.
      So, let's point new contributors to a mirror where they can use the common "fork
      and send a MR" workflow :)
  10. 11 Jul, 2019 2 commits
  11. 02 Jun, 2019 1 commit
    • intrigeri's avatar
      APT repo doc: fix condition. · 872a2218
      intrigeri authored
      A "Debian Maintainer" does not necessarily have any upload rights
      to Debian, so they might want these settings as well. But
      someone with uploads rights to Debian probably won't want them.
  12. 01 Jun, 2019 1 commit
  13. 22 Mar, 2019 1 commit
  14. 20 Mar, 2019 2 commits
  15. 18 Mar, 2019 3 commits
    • intrigeri's avatar
      Add HTML anchor. · 32ab8d67
      intrigeri authored
    • intrigeri's avatar
      Custom APT repo: document how to add an APT overlay and find out how the... · b82ce30d
      intrigeri authored
      Custom APT repo: document how to add an APT overlay and find out how the overlay suite for a given topic branch is called.
    • intrigeri's avatar
      Custom APT repo: move relevant info to the place where one is looking when... · 66562a10
      intrigeri authored
      Custom APT repo: move relevant info to the place where one is looking when they want to upload a package.
      The Overview section explains the branch → APT suite mapping, but it's easy to
      miss when one is focused on the "Importing a new package" howto, which can
      waste developer time: if they don't push a branch before uploading,
      their upload will be rejected.
      In practice, there's rarely any reason to follow the doc we have for "Creating
      a new branch" except before uploading a new package. So let's move these
      instructions to where they're needed, i.e. "Importing a new package".
  16. 22 Oct, 2018 1 commit
  17. 05 Sep, 2018 1 commit
  18. 04 Sep, 2018 1 commit
  19. 17 Aug, 2018 2 commits
  20. 05 Jul, 2017 1 commit
  21. 12 Jun, 2017 1 commit
  22. 19 Apr, 2017 1 commit
  23. 18 Mar, 2017 5 commits
  24. 17 Mar, 2017 1 commit