... | ... | @@ -17,21 +17,27 @@ |
|
|
## The Issue Tracker
|
|
|
|
|
|
* [ ] reconfigure Coverity to open issues in Gitlab instead of mailing to bind9-bugs?
|
|
|
* [ ] Test confidential issues are not visible to non-ISC users
|
|
|
* [ ] Test creating new non-ISC user accounts
|
|
|
* [ ] Test oauth Facebook
|
|
|
* [ ] Test oauth Github
|
|
|
|
|
|
|
|
|
* [ ] Write an announcement of the new bug submission method and send to bind-users, bind-announce, bind-workers. -- @vicky
|
|
|
* [ ] Edit the bugs.isc.org landing page (which is in RT) to direct bind users to https://gitlab.isc.org/isc-projects/bind9/issues
|
|
|
* [ ] Edit the bugs.isc.org landing page (which is in RT) to direct bind users to https://gitlab.isc.org/isc-projects/bind9/issues @vicky to open ops ticket
|
|
|
* [ ] 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]
|
|
|
* [ ] Update the webpage https://www.isc.org/community/report-bug/ to have links to ISC GitLab (12. February 2018) -- @vicky
|
|
|
* [ ] Update the webform found at https://www.isc.org/community/report-bug/ to:
|
|
|
* [ ] Send BIND Confidential Bugs to security-officer@isc.org -- @vicky
|
|
|
* [ ] 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
|
|
|
* [ ] 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
|
|
|
|
|
|
* [ ] update the developer/contributor guide which is packaged with BIND (as well as on the web site and github)
|
|
|
* [ ] update the readme on the BIND github project page to direct ppl to enter issues on gitlab.isc.org or via the form on the web site
|
|
|
* [ ] update the section of the web site on contributing (https://www.isc.org/git/guidelines/, https://www.isc.org/git/bindsubmitters/)
|
|
|
* [ ] update the developer/contributor guide which is packaged with BIND (as well as on the web site and github) @each
|
|
|
* [ ] update the readme on the BIND github project page to direct ppl to enter issues on gitlab.isc.org or via the form on the web site @each
|
|
|
* [ ] update the section of the web site on contributing (https://www.isc.org/git/guidelines/, https://www.isc.org/git/bindsubmitters/) @vicky
|
|
|
|
|
|
* [ ] Walk through existing issues in RT (bugs.isc.org) and manually copy those that still need attention
|
|
|
* [ ] Consider whether we need any additional Issue fields (e.g. for linking to confidential support cases, or for Severity/Priority, or component)
|
|
|
* [ ] 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 Issue and Merge Request templates: https://gitlab.com/help/user/project/description_templates.md |
|
|
\ No newline at end of file |