1. 09 Apr, 2020 1 commit
  2. 03 Apr, 2020 1 commit
  3. 02 Apr, 2020 1 commit
  4. 28 Mar, 2020 1 commit
  5. 11 Jul, 2019 2 commits
  6. 02 Jun, 2019 1 commit
  7. 15 Apr, 2019 1 commit
    • intrigeri's avatar
      Clarify how to set the Assignee field when submitting a branch. · 1f5a8c4f
      intrigeri authored
      As Ulrike pointed out:
      
       - The previous phrasing was very unclear.
       - It's hard to guess whether the FT is able and willing to handle
         a given review. Better let them decide.
       - It's not obvious how one can try to find a reviewer by themselves;
         while regular contributors should hopefully have no trouble doing so,
         new contributors would be left in doubt.
      
      So let's make the default case "empty the Assignee field" and whoever
      is handling the FT's frontdesk role at a given time (for now: yours truly;
      some day: rotating role) will dispatch reviews adequately. And hopefully,
      other team leads have some kind of view that helps the detect pending
      reviews in their own area, without relying on the FT.
      
      refs: #16650
      1f5a8c4f
  8. 08 Apr, 2019 1 commit
    • 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
  9. 05 Apr, 2019 2 commits
  10. 04 Apr, 2019 3 commits
  11. 03 Apr, 2019 2 commits
  12. 02 Apr, 2019 1 commit
  13. 07 Mar, 2019 3 commits
    • intrigeri's avatar
      Reorder. · 1cb33739
      intrigeri authored
      Setting correct metadata should happen before asking for a review, regardless of
      the Jenkins status and the kind of review that's requested.
      1cb33739
    • intrigeri's avatar
      Fix formatting. · bb7ba081
      intrigeri authored
      bb7ba081
    • intrigeri's avatar
      Submitting code: give more flexibility. · ba02e25f
      intrigeri authored
      Thanks to Sandro Knauß <hefee@debian.org> for the feedback
      that lead me to open the door to different workflows.
      ba02e25f
  14. 04 Jan, 2018 1 commit
  15. 02 Jan, 2018 1 commit
  16. 09 Dec, 2017 1 commit
  17. 12 Nov, 2016 1 commit
  18. 15 Apr, 2016 1 commit
  19. 15 Mar, 2016 3 commits
  20. 01 Jul, 2015 1 commit
  21. 13 Dec, 2014 3 commits
  22. 19 Jul, 2014 4 commits
  23. 04 Mar, 2014 1 commit
  24. 27 Jul, 2013 2 commits
  25. 14 Oct, 2012 1 commit