1. 12 Apr, 2019 2 commits
  2. 11 Apr, 2019 1 commit
  3. 09 Apr, 2019 3 commits
  4. 08 Apr, 2019 5 commits
    • intrigeri's avatar
    • intrigeri's avatar
      Allow submitting code for review without waiting for Jenkins to run the entire test suite. · 02c43ba4
      intrigeri authored
      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.
      02c43ba4
    • intrigeri's avatar
      Calendar: remove past events. · 29bcdf4c
      intrigeri authored
      29bcdf4c
    • 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
    • intrigeri's avatar
      Release process: generate the expected OpenPGP signature verification output... · 40aa8198
      intrigeri authored
      Release process: generate the expected OpenPGP signature verification output 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.
      40aa8198
  5. 07 Apr, 2019 9 commits
  6. 06 Apr, 2019 1 commit
  7. 05 Apr, 2019 18 commits
  8. 04 Apr, 2019 1 commit