On Tue, Feb 28, 2012 at 11:06 AM, Jukka Zitting <jukka.zitt...@gmail.com>wrote:
> Hi, > > On Tue, Feb 28, 2012 at 9:59 AM, Alex Karasulu <akaras...@apache.org> > wrote: > > Cloudera's compatibility issues are not our problem. These packages need > to > > go. > > Citation needed. I did not think we needed one: nor do I have one. It's common sense to me that this causes issues. It combines the namespace of a foreign mark with our own. We should not be releasing anything in the namespace belonging to another entity. > Without a written policy to that effect these things > are up for each project to decide. Jarek's rationale sounds perfectly > fine to me. > > I highly respect you opinion here but I disagree regarding this argument provided. There may be no policy to cite, and there may be examples of where this was done before for the sake of backwards compatibility. It still does not justify doing it. > We have plenty of projects that provide such backwards compatibility > wrappers or otherwise put stuff in non-apache namespaces for various > reasons. See for example [1] or [2]. > > Understood. Examples are solid points supporting the argument but IMHO I think this was a mistake that opens the door to several issues. Maybe we need some clear policy regarding the matter. I'm more than ready to be proven wrong on this matter so long as it does not present problems down the line for us. > [1] > http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javahl/ > [2] http://svn.apache.org/repos/asf/geronimo/specs/trunk/ > > BR, > > Jukka Zitting > > -- Best Regards, -- Alex
