I've added more on the limitations of the current process (not
synchronised releases, not enough automated testing on multiple-host
clusters), and on a risk of the project: the upstream projects need to
care about and work on more synchronized releases.
Cloudera managed to address that problem by patching their forks of the
apache projects, then push back the patches by way of JIRA patches.
Bigtop should not get into the game of having its own branches of any of
the ASF projects, instead it should focus on getting its changes into
trunk of the various projects SVN trees, and on having near-synchronized
releases of the various projects
That requires
-engagement from the committer teams to get patches in. Having
committers from the relevant projects in the BigTop project would
address this.
-support from the PMCs to do releases on a regular schedule. That's
hard, but something like a six-monthly schedule for the big projects
with the up and coming projects releasing in a proper factor of that
timescale (3, 2, 1 month), could help.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
