On Tue, Feb 28, 2012 at 1:06 AM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > 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. Without a written policy to that effect these things > are up for each project to decide. Jarek's rationale sounds perfectly > fine to me. > > 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]. > > [1] > http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javahl/ > [2] http://svn.apache.org/repos/asf/geronimo/specs/trunk/ >
I agree with Jukka on this. There is no such policy. There are examples of well established TLPs doing similar. The files are explicitly deprecated and will be eventually removed, they are for the convenience of users and others building on top of Sqoop who are migrating from the original code base to Apache based packages. It makes total sense to provide a bridge that enables that group to move to the Apache version of the code. Patrick --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
