Thanks for taking a look at the report John Russell.
If I create a docs JIRA, e.g. https://issues.apache.org/jira/browse/IMPALA-5326 , is that going to end up in the report or is there a way to label/filter those out?
There is no way to filter those out using the release notes flow from Jira. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321021&version=12340208 shows
IMPALA-3398, IMPALA-4984, and IMPALA-5006. For Apache Impala (incubating), I don't necessarily see a reason to filter these out.
Do we know all the JQL clauses for the new features list produced by JIRA?
No. My guess it's a simply "fixed in <version>" list group-by type. I have not done a thorough cross reference of this, though.
Missed by your filter because its component is infrastructure. I'll follow up to make sure that's correct.
I looked into this, and it's a Jira bug. https://jira.atlassian.com/browse/JRASERVER-20788 When filtering on NOT IN with labels (or any nullable field that supports NOT IN, I guess) you need to include OR labels IS EMPTY. If I adjust your JQL, these get included.
Can the JIRA-produced one also be fine-tuned to omit 'duplicate' ones?
Unfortunately not, since there is no way to have JQL in Jira-produced release notes. But yours can, if you include AND resolution = "Fixed".
Or is it worthwhile to let both original + duplicate JIRAs appear in the list?
In an ideal changelog, this is not worthwhile.
Last, John Russell, not said, but implied here, is that you rely heavily on the "New Feature" issue type to produce documentation, and we should encourage contributors to use this correctly. For example, if I add new testing infrastructure, you would prefer that not be included as a "New Feature", because it's not a new feature of Impala proper, right?