lidavidm commented on issue #1358: URL: https://github.com/apache/arrow-adbc/issues/1358#issuecomment-2303602788
> I gather from another issue that we're gearing up for a release soon, and I'm a bit embarrassed to admit that the release schedule is completely opaque to me. Is it the case that both the core Arrow project and the ADBC subproject are on a bimonthly release cadence, but on alternating months? We're independent of the core project. I've been trying to aim for a release every 6-8 weeks (mostly depends on my schedule and if I remember to look at the calendar...) > Regardless, it seems that there's almost certainly not enough time to get this change in for the very next release, but I'd like to try to drive this item and a bunch of other API changes on the backlog and combine them into a 1.2 version of the spec for the subsequent release. I think for 1.1, I created a branch and merged everything there over the course of a few releases, then when it was ready did the big merge into the main branch for a release. That might be better since (1) I'd rather batch up changes as much as possible to limit how often we change ABI and (2) that'll give everyone more time to work through changes. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
