jonkeane commented on issue #10: URL: https://github.com/apache/arrow-cookbook/issues/10#issuecomment-896619052
As a slight extension of what Neal is proposing (and adding something Weston mentioned) we could take the approach of not backporting/maintaining old versions of the cookbook when we release a new version of arrow (they are kept with the exact same content that they had before). And also (especially while we are actively expanding that coverage of the cookbook) we mention what version a feature became available in. That way if we do add a long-standing feature to the cookbook, someone could look at the latest cookbook and see "oh this is available starting in version 2.0, I'm on version 3.0 and arrow is on version 5.0 — so I should be good to use this" -- 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]
