Closing the loop on seeking consensus for UX/UI/API changes, I see a few options. Can we rank choice vote please?
A - Jira suffices B - Post a DISCUSS API thread prior to making changes C - Periodically publish a list of API changes for retrospective consideration by the community Points raised in the discussion included: lowering the bar for participation and avoiding unnecessary burden to developers. I vote B (only) because I think broader participation is most important for these topics. > On 7 Dec 2022, at 15:43, Mick Semb Wever <m...@apache.org> wrote: > >> I think it makes sense to look into improving visibility of API changes, so >> people can more easily review a summary of API changes versus reading >> through the whole changelog (perhaps we need a summarized API change log?). > > > Agree Paulo. > > Observers should be able to see all API changes early. We can do better than > telling downstream users/devs "you have to listen to all jira tickets" or > "you have to watch the code and pick up changes". Watching CHANGES.txt or > NEWS.txt or CEPs doesn't solve the need either. > > Observing such changes as early as possible can save a significant amount of > effort and headache later on, and should be encouraged. If done correctly I > can imagine it will help welcome more contributors. > > I can also see that we can improve at, and have a better shared understanding > of, categorising the types of API changes: > addition/change/deprecation/removal, signature/output/behavioural, API/SPI. > So I can see value here for both observers and for ourselves. >
