summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* This reverts commit e008e3be304eee9c6e1acb7fa04789bf1cef4eee127.0.0.12019-04-121-11/+0
|
* This reverts commit aee5314a38c6875b344cf32c31b3c13ae4e6dd10127.0.0.12019-04-121-2/+4
|
* This reverts commit 4fc1504f78f6382e9bdc2eca6adc7f042aed760a127.0.0.12019-04-121-2/+2
|
* Merge remote-tracking branch 'origin/master'intrigeri2019-04-127-22/+30
|\
| * Curators++sajolida2019-04-121-2/+2
| |
| * updated PO filesIkiWiki2019-04-126-20/+28
| |
* | Design doc: fix ticket number.intrigeri2019-04-121-1/+1
|/
* Merge remote-tracking branch 'origin/doc/16408-usb-image-virt-manager'intrigeri2019-04-121-1/+1
|\ | | | | | | Closes: #16408
| * Don't use OS type "Generic default" in virt-manager (refs: #16408)segfault2019-03-231-1/+1
| | | | | | | | | | | | | | On my system (Debian Sid), new machines I create with OS type "Generic default" miss the spice channel required to share the clipboard between host and guest. When I create the machine as "Debian Stretch", this channel is automatically added.
* | Add more resources about automated testing of Secure Boot.intrigeri2019-04-111-0/+11
| |
* | Add my bits of the monthly reportsajolida2019-04-092-20/+60
| |
* | (no commit message)127.0.0.12019-04-091-4/+2
| |
* | Review policy: also assign the MR.intrigeri2019-04-091-2/+2
| |
* | Give Team Managers responsibility to move leftovers of deliverables to UX & ↵intrigeri2019-04-081-0/+5
| | | | | | | | technical debt.
* | Allow submitting code for review without waiting for Jenkins to run the ↵intrigeri2019-04-081-8/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | entire test suite. Let's explicitly allow submitting a branch immediately after running the relevant test suite scenarios locally. This should make it possible for a developer to start working on a ticket and submit the resulting branch for QA in one single work session: while the branch builds on Jenkins, one can run the relevant test suite scenarios locally. I hope this can lower the amount of WIP developers carry and the number of context switches they have to do (refs: #15864). Worst case, we'll notice any test suite regression after the merge; we can then revert the merge and nicely ask the branch submitter to fix the regression before we merge it again.
* | Calendar: remove past events.intrigeri2019-04-081-7/+0
| |
* | Make release notes writing instructions consistent with the implicit ↵intrigeri2019-04-081-2/+2
| | | | | | | | | | | | | | | | 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.
* | Release process: generate the expected OpenPGP signature verification output ↵intrigeri2019-04-081-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | in a more deterministic way (refs: #16585) Using --trusted-key avoids this warning: gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. … and makes our signing key trusted at the "ultimate" level. So let's also s/ultimate/full/ to stick closer to what users should get once they verify our key via the WoT and certify it locally.
* | Revert spam.intrigeri2019-04-074-60/+125
| |
* | This reverts commit f041ce0f9be9784e48b5c4a8479cf77078444499127.0.0.12019-04-071-1/+0
| |
* | This reverts commit 7ef5685b56228122364faeed9937e13a4aa95e6d127.0.0.12019-04-071-0/+1
| |
* | This reverts commit f7e2b39ac4a6641fd3c168778fbc2cae50b69f01127.0.0.12019-04-071-58/+46
| |
* | This reverts commit 5465de52a811c2a3b2f5aecb15ad1718a030f7a1127.0.0.12019-04-071-26/+0
| |
* | This reverts commit ed5988a47eaa5b419573c7b10020e74ca471672e127.0.0.12019-04-071-2/+2
| |
* | This reverts commit c9e67474050a6f564b74d94980a8813a98ce4f7d127.0.0.12019-04-071-0/+7
| |
* | This reverts commit 234e4e3586c2fe9805bde78c717f50552338969d127.0.0.12019-04-071-7/+1
| |
* | This reverts commit 21268807d363d9890d54fb8ebfdd07349cfe6a22127.0.0.12019-04-073-36/+8
| |
* | Revert spam.intrigeri2019-04-063-8/+36
| |
* | This reverts commit 86867060ec05130291506b3eb7a630a8a12754a6127.0.0.12019-04-051-1/+0
| |
* | This reverts commit 1301efeab0fe20cb866d0c64ac9c8316896a0522127.0.0.12019-04-051-1/+0
| |
* | This reverts commit 00e52c33a5aaae68053e619cac337a2d5203761d127.0.0.12019-04-051-34/+8
| |
* | Add HTML anchors.intrigeri2019-04-051-0/+4
| |
* | Move corner case that's hard to understand to the end.intrigeri2019-04-051-4/+4
| | | | | | | | Thanks to u for the feedback!
* | Improve phrasing.intrigeri2019-04-051-4/+5
| | | | | | | | Thanks to u for the feedback!
* | Foundations Team: add another case where setting an Assignee makes sense.intrigeri2019-04-051-0/+2
| |
* | Merge remote-tracking branch 'origin/master'intrigeri2019-04-0515-20/+143
|\ \
| * | updated PO filesIkiWiki2019-04-056-6/+73
| | |
| * | Add Dell model that seems to have boot issues.Ulrike Uhlig2019-04-051-0/+4
| | |
| * | Merge branch 'master' of d53ykjpeekuikgoq.onion:tailsUlrike Uhlig2019-04-056-6/+30
| |\ \
| | * | updated PO filesIkiWiki2019-04-056-6/+30
| | | |
| * | | Add bits to monthly reportUlrike Uhlig2019-04-051-8/+34
| |/ /
| * | We received a large donation from a group of people.Ulrike Uhlig2019-04-051-0/+2
| | |
| * | Merge branch 'master' of d53ykjpeekuikgoq.onion:tailsUlrike Uhlig2019-04-05116-960/+2726
| |\ \
* | | | Document the Foundations Team's principles and guidelines for tasks management.intrigeri2019-04-051-0/+83
| |/ / |/| |
* | | Revert "One needs to push to Salsa as well in order to create a MR."intrigeri2019-04-051-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | I was wrong, thanks hefee for correcting me: a developer with commit access to our canonical repo can very well push there, which will propagate to the Salsa mirror repo, and then browse the Salsa web UI to click "Create merge request". This reverts commit bd8cd79ca7e611b4211c58d353c8f653fd114f8c.
* | | One needs to push to Salsa as well in order to create a MR.intrigeri2019-04-051-1/+2
| | |
* | | Number list: order matters here.intrigeri2019-04-041-28/+28
| | |
* | | Document where to push "code" branches for review (refs: #15186).intrigeri2019-04-041-0/+5
| | | | | | | | | | | | | | | | | | | | | Let's not implicitly suggest one can push directly to our repository on Salsa: it's meant to be a read-only mirror of our canonical repo, and any changes made directly on Salsa will be overwritten next time someone pushes _anything_ to the canonical tails.git.
* | | Recommend forking Git on Salsa for "code" work (refs: #15186).intrigeri2019-04-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | - Salsa because we have merge requests enabled there, while we don't have them on gitlab.com (both on purpose). - Only for "code" work: for now, only the FT is ready to deal with merge requests sent on GitLab.
* | | Clarify Secure Boot requirements.intrigeri2019-04-041-1/+7
| | |