Instead of a static PR template, we could create a GH workflow that generates a draft PR for the release blog based on an array of JDK versions covered under a particular release. This can also fetch info from the temurin-vdr-generator vdr.json file in future.
The draft will still need to be manually updated and reviewed to include the comments in the release blog post issue to capture new and noteworthy.
Instead of a static PR template, we could create a GH workflow that generates a draft PR for the release blog based on an array of JDK versions covered under a particular release. This can also fetch info from the temurin-vdr-generator vdr.json file in future.
The draft will still need to be manually updated and reviewed to include the comments in the release blog post issue to capture new and noteworthy.