-
Notifications
You must be signed in to change notification settings - Fork 301
Release Notes – gathering data
Clemens Lieb edited this page Aug 16, 2020
·
1 revision
In the release notes we're providing a few interesting tidbits.
The first is the number of bugs we've fixed since the last green release. The information for that is obtained from basic github search, using the query:
is:issue is:closed label:bug closed:>=YYYY-MM-DD -label:duplicate -label:status-ignored -label:status-norepro -label:status-declined -label:status-deferred -label:status-bydesign
We also note how many of these bugs were known at the time of the last green release, by adding created:<=YYYY-MM-DD
to the query.
Adjusting the label filters also allows us to give a number of enhancements implemented with the query:
is:issue is:closed label:enhancement -label:bug closed:>=2019-12-22 -label:duplicate -label:status-ignored -label:status-norepro -label:status-declined -label:status-deferred -label:status-bydesign
We also grab the number of commits to next since the last green release from the pull request that merges the state of "next" into "master"
All of this information can then be aggregated in the following template:
This version fixes [#1 bugs][fixed-bugs], [#2][known-before] of which were known issues at the time of the release of v...;
[#3 enhancement issues][enhancements] were closed in this development cycle, in #4 commits.
rubberduckvba.com
© 2014-2021 Rubberduck project contributors
- Contributing
- Build process
- Version bump
- Architecture Overview
- IoC Container
- Parser State
- The Parsing Process
- How to view parse tree
- UI Design Guidelines
- Strategies for managing COM object lifetime and release
- COM Registration
- Internal Codebase Analysis
- Projects & Workflow
- Adding other Host Applications
- Inspections XML-Doc
-
VBE Events