Greetings mesos-devel - As some of you are aware, I've been working on packaging a mesos.rpm for Fedora. Some of the details can be found in the links below:
- https://bugzilla.redhat.com/show_bug.cgi?id=1010512 - https://fedoraproject.org/wiki/SIGs/bigdata/packaging/Mesos However, in order for me to get to this point, I had to substantially change the build mechanics to meet downstream guidelines. What has become apparent to me in this effort is the need to clean/scrub/reform/audit, the build process. I've written a quick proposal here: https://issues.apache.org/jira/browse/MESOS-898. As I've mentioned in the JIRA, I've done this on large scale projects before. However, I've learned the key to making this succeed is ensuring there are upstream champions that support the idea, along with a process on how to accept changes that could be "temporarily destabilizing". (e.g. Having stable+unstable branching strategy) There is always a cost associated with this type of work, but IMHO the long term benefits are worth it during this nascent phase. I would greatly appreciate your feedback on the JIRA mentioned above. -- Cheers, Tim
