cederom commented on PR #16280: URL: https://github.com/apache/nuttx/pull/16280#issuecomment-2839037475
> > > @cederom: Thank you guys! I just wonder how to communicate the change to folks that may use existing functionality and what would be the proposed fix to get the same behavior after update (i.e. send logs to /dev/null) :-) > > > > > > @michallenc: This might be a silly idea, but adding preprocessor `#warning` could warn about the change for some time. The problem is this code is compiled by default, so it would pop up to everyone... > > @hartmannathan: I think the release notes should clearly state the breaking changes. Currently we just link to each PR, which is more like a Changelog than a Release Notes. Release Notes should be more like documentation. In the release notes, each breaking change should tell developers what they need to change in their code to avoid the surprise breakage. Thanks to the [BREAKING] tag the changelog will show breaking changes clearly :-) Yes it would be nice to have a workaround proposition bundled unless there is one :-P -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
