If the big works are already accompanied by discussions, I do not see a reason a list pointing to Jira tickets with small API changes could not serve our needs. A nice label and commitment that API change will be brought in the description with a few sentences seems more than enough to me.
Also, I am confused… when I asked about the access of JDK internals which can lead to trouble, breaking changes and urgent patches needed, we agreed Jira is enough and we shouldn’t trigger too much noise here, but for small API changes this is preferable? What do I miss here? Maybe there is something more that people have in mind that I struggle to see? On Tue, 6 Dec 2022 at 8:53, Benjamin Lerer <b.le...@gmail.com> wrote: > I am sorry but I still do not understand what problem we are trying to > solve. > All examples given so far have been about significant features which we > already discuss on this mailing not about minor changes that happen > multiple times per week. > Is it a trust issue ? >
