I’m not opposed to this, although I think there is less need for it. Do you have an example of where you think this policy could have resulted in a different outcome?
> On 1 Sep 2022, at 16:31, Ekaterina Dimitrova <e.dimitr...@gmail.com> wrote: > > Hi everyone, > > Some time ago we added a note to the project Cassandra Code Style: > “New dependencies should not be included without community consensus first > being obtained via a [DISCUSS] thread on the dev@cassandra.apache.org mailing > list” > > I would like to suggest also to add a point around accessing JDK internals. > Any patch that suggests accessing internals and/or adding even more > add-opens/add-exports to be approved prior commit on the mailing list. > > It seems to me the project can only benefit of this visibility. If something > is accepted as an exception, we need to have the right understanding and > visibility of why; in some cases maybe to see for alternatives, to have > follow up tickets opened, ownership taken. In my opinion this will be very > helpful for maintaining the codebase. > > If others agree with that I can add a sentence to the Code Style. Please let > me know what you think. > > Best regards, > Ekaterina > >
