ChatPGT prompt to search for interesting release notes

gistfile1.txt

Analyse all the bugs that landed during the 152 nightly cycle. 
The goal is to identify new features and important changes and create release notes for end-users. 
I am providing you a json file that contains data for all the bugs that were included during the 152 development cycle. 
This JSON is an export of all the bugs from bugzilla.mozilla.org via its public API. 
The bugzilla documentation for the API is here https://bmo.readthedocs.io/en/latest/api/index.html 

In our release notes we have several sections: 
NEW 
FIXED 
CHANGED 
FIREFOX LABS
ENTERPRISE 
WEB PLATFORM 
DEVELOPER TOOLS

- Firefox Desktop and Gecko platform bugs, ignore Android bugs.
- List the top 50 most important bugs with Bugzilla IDs, generate a table and a final link to the bug list
- Exclude crash fixes
- Exclude bugs still in an open state
- Exclude all the bugs that are not marked as verified or fixed for the status of the field cf_status_firefox152
- Exclude all the bugs that are marked as verified or fixed for the status of the field cf_status_firefox147
- Exclude telemetry related bugs
- Exclude web compatibility bugs
- Exclude Thunderbird bugs
- Rank new features higher than others
- Focus more narrowly on end-user-visible UI/platform changes
- If the status field for 151 on a bug is set to "fixed" or "verified", that means that this bug was uplifted ans shipped into Firefox 151. Those bugs should not be in release notes for 152
- if the relnote-firefox flag is set to a question mark or to 152+, exclude the note from the results.
- Do not merge multiple features in a single note, have a note per bug

- Generate a second list of bugs fixed with multiple duplicates
- Generate a third list of the 20 oldest bugs fixed 
- Linkify all bugs in your response to bugzilla bugs, make sure those bugs match what you output.