Re: Documentation of Breaking Changes

2023-11-22 Thread Chris Thomas
order to do that. Once this is > done we could modify our Changelog script to build a section with > Breaking changes to make it easier for users to find those. > > [1] > https://github.com/apache/arrow/issues?q=label%3A%22Breaking+Change%22+milestone%3A13.0.0 > [2] https://g

Re: Documentation of Breaking Changes

2023-11-21 Thread Chris Thomas
2023/08/24/13.0.0-release/ > [3] https://github.com/apache/arrow/labels > [4] https://arrow.apache.org/docs/developers/reviewing.html#labelling > [5] https://arrow.apache.org/release/13.0.0.html#changelog > > On Tue, Nov 21, 2023 at 1:00 PM Chris Thomas wrote: > > > > Evening folks, &g

Documentation of Breaking Changes

2023-11-21 Thread Chris Thomas
gs for the package are a verbose dump of all of the PRs included in the release. Working out which of them constitute a breaking change and what the implications are of that change is difficult. Is this something that could be addressed in the project? -- Best, Chris Thomas Engineering Manager