[GitHub] [arrow-cookbook] westonpace commented on issue #11: [DISCUSS] Handling Arrow Versioning

[GitBox <gi...@apache.org>]

westonpace commented on issue #11:
URL: https://github.com/apache/arrow-cookbook/issues/11#issuecomment-1009285835


   It's been a while but I guess my thinking was that this question was superseded by discussion in #10 .
   
   I think it's good to allow recipes to be developed prior to the feature being released so having some way to mark them would be good.  In general, we probably want some way to mark which versions a particular recipe supports anyways.
   
   At one point in time I had even brainstormed a little how we might support this in the C++ cookbook.  The start recipe macro could take an (optional) minimum version and an (optional) maximum version and then use that information to allow multiple versions of a recipe and make sure to include the min/max on the page when it is being viewed.  However, that thought never made it past brainstorming and each cookbook will have to figure out some way of managing 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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org