Putting that information in the release note is certainly
convenient, but...
I tend to use the release note for information that developers
downloading the release will need to know, and I think most
developers won't have any interest in the TCK results so adding them
there would just clutter the release note.
I think it's better to put the TCK results in the source code repo
or the web site repo (e.g., gh-pages) or the wiki for the project,
and then just link to them from the release review PR.
Scott Stark wrote on 7/17/19 12:03 PM:
+1 for simply defining a GitHub release template for EE4J
projects.
There is no inherent support for release templates
in the way one can create a PR template, but there is this app:
That has this codebase:
We can certainly define a GitHub markdown template
file one can pasted into the release content when creating it.
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
|
