opened
bryevdv
username_0
cc @username_1 

In light of the process changes that will come out of #10177, the `scripts/issues.py` tool will need updates. 

also ref: https://github.com/bokeh/bokeh/wiki/BEP-1:-Issues-and-PRs-management

There are three modes that this script will be used:

#### Release Validation Mode

Would like to be able to run the script in automation to ensure that all the relevant issues are labeled appropriately, etc. Some criteria:

* Relevant issues/PRs are those for the current specified milestone
* All issues in the milestone should be closed, with a `reso:completed`
* All PRs in the milestone should be closed/merged with `status:accepted`
* Any PR with a `type` label (an "issue PR") also needs `reso:completed`
* There should only ever be one `reso` or `status` label applied.

```shell
python issues.py check --release 2.1.1  # check issues/PRs in 2.1.1 milestone
```

#### General Validation Mode

Would like to be able to run the script manually, periodically, to check all issues in the last N months for label (or since a specified tag?) 

* Relevant issues/PRs are those for since the specified event or time
* All closed  issues should have one `reso:` label
* All closed PRs should have one `status:` labels
* Any closed PR with a `type` label (an "issue PR") also needs a `reso` label
* Open issues/PRs should not have any `reso` or `status` label applied.

```shell
python issues.py check --tag 2.0.2  # check all issues/PRs since 2.0.2 tag

python issues.py check ?? # check all issues/PRs in last N months?
```

#### Release Update Mode

Would like to be able to run the script in automation to update the CHANGELOG with lists of issues (or "issue PRs") from the current milestone. 

* Group by bugfix, feature, task
* Include component label, if present

```shell
python issues.py update --release 2.1.1 # update CHANGELOG with issues/PRs in 2.1.1 milestone 
```
Implies a check?
Issues / Changelog script will need update 
issue
created
lexicalunit
username_1
## Check Only Mode
- [ ] Relevant issues/PRs are those for the current specified milestone
- [ ] All issues in the milestone should be closed, with a reso:completed
- [ ] All PRs in the milestone should be closed/merged with status:accepted
- [ ] Any PR with a type label (an "issue PR") also needs reso:completed
- [ ] There should only ever be one reso or status label applied.
- [ ] All issues sholud have a type
- [ ] Allowed types: bug, feature, task
- [ ] Nothing should have TRIAGE label
- [ ] All issues/PRs should be closed

## Update Mode
- [ ] Should do all the checks from check only mode first
- [ ] Group by bugfix, feature, task
- [ ] Include component label, if present
comment
created
bryevdv
username_0
closed by #10245
comment
closed
bryevdv
username_0
issue