westonpace commented on issue #10: URL: https://github.com/apache/arrow-cookbook/issues/10#issuecomment-894080452
So I thinking this over and had a couple of thoughts. First, it would probably be good if each implementation had the freedom to adopt a strategy that works for them. We don't want to discourage an implementation from getting started by setting a high bar. Second, I think there are a few levels to choose from: 1. No guarantees. Each build of the cookbook is run against the latest (source or nightly) build of Arrow. This is the only testing that is done. New features are added immediately. 2. One version of recipes, multiple versions of Arrow. There is only one cookbook. For every recipe the cookbook would need to provide which version of Arrow it supports. CI would then run multiple passes with multiple builds of Arrow (e.g. one CI run might test against 3.0 and 4.0 and 5.0. Each pass would verify more and more recipes. 3. Multiple versions of recipes, multiple version of Arrow. This is similar to option 2 but a cookbook could have the same recipe multiple times for multiple versions (e.g. this is how you do XYZ on versions 3-5 and this is how you do XYZ on versions 6+). The website would need some kind of version selector dropdown. The cookbook would need #ifdef type capabilities to pick which recipes to run on which versions of Arrow. CI would still need multiple passes of Arrow. The one approach I think we should NOT do is: Every build we test against the latest released version of arrow and new recipes can only be added after the particular feature has been released. I feel this will discourage Arrow developers from contributing to the cookbook as they add new content. By the time Arrow has released they might not be so interested in the feature anymore or they may have forgotten details. -- 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]
