I support Doug's idea whole-heartedly. The question that remains is "who gets to test and stabilize this new branch"? I am proposing that we designate a owner for this branch and it is the onus of the owner of this branch to test/stabilize that branch.
thanks, dhruba On Fri, Apr 23, 2010 at 1:51 PM, Doug Cutting <[email protected]> wrote: > Chris Douglas wrote: > >> From a technical perspective, nothing has >> been more destructive to the momentum and focus of this project than >> the perpetual backporting and development on this branch. >> > > I'm not proposing any more back- or forward-porting than will be done > anyway. I'm proposing we commit all the 0.20 security patches to a repo at > Apache. This could be as simple as copying Y!'s github repo wholesale to a > branch at Apache. Or, with a bit more effort, we can probably apply the > patches from Jira in the right order. Otherwise, Cloudera, Facebook and > others will have to duplicate this effort. Then bugfix patches and releases > can be made against this repo rather than everyone having to assemble and > maintain their own 0.20 security patchset from scratch. Everyone will be > using this patchset for quite some time. Why shouldn't we share a repo that > contains it? > > Doug > -- Connect to me at http://www.facebook.com/dhruba
