Dear Neil,
Please share your ideas here! What I've tried is to re-generate the sig
files, so they would be up to date (User ant gen-sig-tests, I hope I'm
right about that).
Right now it does not show any difference between the existing and newly
generated files. Though I might do something wrong here.
On 10/22/20 10:44 AM, Neil C Smith wrote:
On Thu, 22 Oct 2020 at 01:35, Laszlo Kishalmi <[email protected]> wrote:
I'm sorry, I was holding it off for ...
Yes, no problem, I was just wondering if you'd had a thought how to
do, because I realized I'd had a couple of thoughts after that PR
conversation that I hadn't followed up on.
Basically, had thought we'd generate a PR to master for this after
first beta (or second now), but not merge. Then after each beta, the
PR gets an update (if needed) - that way the review process for sigs
is actually useful and can be tracked. Signature review then forms
part of release review, any concerns can be addressed before release,
and the PR can be updated, squashed and merged to master after
release.
Thoughts? Happy to have a look at producing the PR if you want?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
