jorisvandenbossche commented on issue #10: URL: https://github.com/apache/arrow-cookbook/issues/10#issuecomment-896036756
> I think that could be a workable solution. I do think you will end up with a lot of cookbooks and then if you find a grammar issue for example you have to fix it in several places. That being said, you could always have a limit on how many versions of Arrow we support. The question is then indeed how long we intent to maintain the "older" cookbooks? Because it sounds a maintenance burden to actively maintain multiple versions .. That might be a good reason, while the content is still growing in a faster pace, to not yet have separate versions. If it's mainly about recipes that use *new* features that are not yet available in older versions, then for now we could maybe also include some standard text like "Requires Arrow x.x" where needed. -- 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-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
