Hi, the last couple of days I have been investigating the Cascading integration for Bigtop. I have navigated the project and created RPM files for two of our projects. Since we are outside of the ASF, things tend to be a bit different, but I got it to work. I am currently doing the same for the debian packages, which should not take too much time.
Now to my actual questions: Bigtop supports a number of distributions and has CI infrastructure to build the packages. I am wondering how we as the Cascading community can work with that infrastructure for better integration, or if we have to replicate all of it. Let me know, what could work best. I'd love to test and build all packages in an easy way, but going through JIRA with a commiter reviewing and committing it looks like a pretty heavy process. OTOH if I replicate the infrastructure I will end up having to catch up with all infrastructure changes all the time. I am unsure what your way of maintaining things is, once a Bigtop release is made. I guess you are not targeting a rolling release, but rather a stable release to be used for a longer time. How do bugfix releases for packages go in? Suppose we have a Cascading tool version x.y in Bigtop a.b. and we make a critical bugfix release x.z, which we want to distribute to Bigtop users as well. Would that then require a complete Bigtop release with voting and all that or do you envision a faster track like linux distros, which update packages for a given release. Thanks for your answers! - André -- André Kelpe [email protected] http://concurrentinc.com
