|
|
## GitLab
|
|
|
* [x] Open the public BIND9 repository to public (2. February 2018) -- @ondrej
|
|
|
* [x] Switch GitLab CI to ISC's GitLab Runners -- @ondrej
|
|
|
* [ ] Setup regular backups for ISC's GitLab -- [ISC-Ops #85574]
|
|
|
* [x] Setup regular backups for ISC's GitLab -- [ISC-Ops #85574]
|
|
|
* [x] Make other people admins in GitLab (@stephen and @tomek) -- @ondrej
|
|
|
|
|
|
## Git Repository
|
|
|
|
|
|
* [ ] Switch the BIND9 main repository from repo.isc.org to gitlab.isc.org
|
|
|
* [x] Switch the BIND9 main repository from repo.isc.org to gitlab.isc.org
|
|
|
* [x] Make the repo.isc.org repository read-only (12. February 2018 09:00 UTC)
|
|
|
* [x] Sync the public parts of repo.isc.org repository to gitlab.isc.org (12. February 2018 09:00-10:00 UTC)
|
|
|
* [?] Developers will change their origin to git@gitlab.isc.org:isc-projects/bind9.git (12. February 2018 10:00)
|
|
|
* [x] Developers will change their origin to git@gitlab.isc.org:isc-projects/bind9.git (12. February 2018 10:00)
|
|
|
* [ ] Redirect the https://source.isc.org/git/bind9.git to https://gitlab.isc.org/isc-projects/bind9.git (12. February 2018 10:00+)
|
|
|
* [x] Decide what to do with TinderBox User changes (honestly, it clutters the commit log a lot: https://gitlab.isc.org/isc-projects/bind9/graphs/master)
|
|
|
* [ ] Kill the TinderBox User and update the copyright 1/1 every year #55
|
|
|
* [ ] Verify that external contributors can submit merge requests
|
|
|
* [x] Kill the TinderBox User and update the copyright 1/1 every year #55
|
|
|
* [x] Verify that external contributors can submit merge requests (upon request)
|
|
|
|
|
|
## The Issue Tracker
|
|
|
|
... | ... | @@ -30,7 +30,7 @@ |
|
|
* [x] Edit the bugs RT autoresponder to saying that new BIND issues are to be filed at https://gitlab.isc.org/isc-projects/bind9/issues, but still create the tickets. (NB the submitters will still get an email back from bugs RT saying their ticket has been created in RT) (12. February 2018 17:00 UTC) -- [ISC-Ops #86014]
|
|
|
* [x] Update the webpage https://www.isc.org/community/report-bug/ to have links to ISC GitLab (12. February 2018) -- @vicky
|
|
|
* [x] Update the webform found at https://www.isc.org/community/report-bug/ to:
|
|
|
* [ ] Send BIND Confidential Bugs to security-officer@isc.org -- @vicky (do we really want this? users can enter confidential bugs in gitlab directly, so why email them?)
|
|
|
* [x] Send BIND Confidential Bugs to security-officer@isc.org -- @vicky (do we really want this? users can enter confidential bugs in gitlab directly, so why email them?)
|
|
|
* [ ] Attempt to enter bugs into gitlab via dummy account from the web submission form - may need a separate web submission for for BIND vs DHCP -- @vicky to investigate
|
|
|
* [ ] is there a KB article on filing bug reports? if so, we need to find and update that
|
|
|
* [ ] **Start bouncing the emails (with the autoresponder on) sent to bind9-bugs (and other email aliases) (5. March 2018 17:00) -- support or ops**
|
... | ... | @@ -40,6 +40,6 @@ |
|
|
* [x] update the section of the web site on contributing (https://www.isc.org/git/guidelines/, https://www.isc.org/git/bindsubmitters/) @oerdnj
|
|
|
|
|
|
* [ ] Walk through existing issues in RT (bugs.isc.org) and manually copy those that still need attention (possible all-hands project?)
|
|
|
* [ ] Create a standard process for logging customer issues (e.g. tag as confidential, link the associated support ticket in the body ...)@cathya
|
|
|
* [ ] Create a standard process for logging customer issues (e.g. tag as confidential, link the associated support ticket in the body ...) @cathya
|
|
|
|
|
|
* [ ] Create Issue and Merge Request templates: https://gitlab.com/help/user/project/description_templates.md |
|
|
\ No newline at end of file |