Thanks guys. I've added a separate release vehicle for the above items.

https://cwiki.apache.org/confluence/display/SQOOP/Sqoop+2+Roadmaps

-Abe

On Mon, Oct 13, 2014 at 6:32 PM, Jarek Jarcec Cecho <[email protected]>
wrote:

> We’ve lastly released Sqoop2 in November last year which is almost a year
> ago. Hence, I’m definitely in favor of releasing something sooner rather
> then later. I think that we already did quite a lot of work, mainly in the
> From/To refactoring that Abe was driving and the clean up in the entity
> names that Veena is driving, that justify a release.
>
> Jarcec
>
> On Oct 13, 2014, at 10:52 AM, Venkat Ranganathan <
> [email protected]> wrote:
>
> > +1
> >
> > On Mon, Oct 13, 2014 at 10:38 AM, Gwen Shapira <[email protected]>
> > wrote:
> >
> >> +1
> >>
> >> On Mon, Oct 13, 2014 at 10:15 AM, Abraham Elmahrek <[email protected]>
> >> wrote:
> >>> Hey guys,
> >>>
> >>> I was reviewing the roadmap and it seems that 1.99.4 has the following
> in
> >>> it:
> >>>
> >>>   -
> >>>
> >>>   Kerberos authentication
> >>>   <https://issues.apache.org/jira/browse/SQOOP-1525>
> >>>   -
> >>>
> >>>   Incremental data transfer
> >>>   <https://issues.apache.org/jira/browse/SQOOP-1168>
> >>>   -
> >>>
> >>>   PostgreSQL repository <
> >> https://issues.apache.org/jira/browse/SQOOP-1120>
> >>>
> >>>
> >>> Think it would be a good idea to move these items to 1.99.5 and do a
> >> 1.99.4
> >>> release sooner rather than later? 1.99.4 should be refactoring and
> >>> stability after all.
> >>>
> >>> -Abe
> >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
>

Reply via email to