You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by Anna Szonyi <sz...@cloudera.com> on 2017/05/12 09:58:26 UTC
Creating feature branches
Hi @devs,
We would like to start the preparation for upgrading to hive 2 (upgrade
version, migrate off of hive cli and onto beeline, etc.).
As we anticipate there being a few patches we were thinking it would make
sense to create a feature branch (sqoop_hive2) for this, as we do not want
trunk to become unstable or introduce "breaking changes" before the
proposed 1.4.7 release.
Does anyone have any concerns about this?
And in general do we have a policy about feature branches for sqoop (like a
sqoop_kerberos branch, etc.)?
Thanks,
Anna
Re: Creating feature branches
Posted by Attila Szabó <ma...@apache.org>.
Hey Bogi,
Thanks for raising this questions. I've just opened a new topic around this.
It would be great if you could share your thoughts there.
Many thanks,
Attila
On Tue, May 23, 2017 at 2:41 PM, Boglarka Egyed <bo...@cloudera.com> wrote:
> Hi Attila,
>
> You mentioned that you have a plan for releasing 1.4.7, could you please
> give an update on that?
>
> Many thanks,
> Bogi
>
> On Tue, May 16, 2017 at 10:35 AM, Szabolcs Vasas <va...@cloudera.com>
> wrote:
>
>> Hi Attila,
>>
>> I don't have a list of JIRAs yet this was just an idea we can implement in
>> the future.
>>
>> Szabolcs
>>
>> On Mon, May 15, 2017 at 6:23 PM, Attila Szabó <ma...@apache.org> wrote:
>>
>> > Hey Szabi:
>> > Do you already have a plan ( I mean a list of JIRA issues for your
>> first
>> > feature branch(es))
>> >
>> > Thanks,
>> > Attila
>> >
>> > On May 15, 2017 3:15 PM, "Szabolcs Vasas" <va...@cloudera.com> wrote:
>> >
>> > > Hi all,
>> > >
>> > > I also like the idea of creating feature branches. As far as I see we
>> > > cannot create Sqoop epics on issues.apache.org so we could use
>> subtasks
>> > to
>> > > track what do we plan to put in a feature branch.
>> > >
>> > > Regards,
>> > > Szabolcs
>> > >
>> > > On Fri, May 12, 2017 at 2:15 PM, Attila Szabó <ma...@apache.org>
>> wrote:
>> > >
>> > > > Hey Anna,
>> > > >
>> > > >
>> > > > On my side: +1 if it helps your development efforts, and if the
>> feature
>> > > > branch won't be a "long living" one. (and of course you would merge
>> it
>> > > with
>> > > > the trunk frequently not to let it diverge too much from other
>> > changes).
>> > > >
>> > > >
>> > > > Related actions (by me):
>> > > >
>> > > > I would like to support your efforts on this side by finalizing the
>> > 1.4.7
>> > > > release dates with the community soon (I'd like to send an email
>> about
>> > > > those efforts still today).
>> > > >
>> > > >
>> > > > On request:
>> > > >
>> > > > Would you please enlist the JIRA tasks you'd like to work on
>> related to
>> > > > that specific feature branch (thus the whole community would be
>> able to
>> > > see
>> > > > the scope of the features you'd working on).
>> > > >
>> > > >
>> > > > Cheers,
>> > > >
>> > > > Attila
>> > > >
>> > > > On Fri, May 12, 2017 at 11:58 AM, Anna Szonyi <sz...@cloudera.com>
>> > > wrote:
>> > > >
>> > > > > Hi @devs,
>> > > > >
>> > > > > We would like to start the preparation for upgrading to hive 2
>> > (upgrade
>> > > > > version, migrate off of hive cli and onto beeline, etc.).
>> > > > > As we anticipate there being a few patches we were thinking it
>> would
>> > > make
>> > > > > sense to create a feature branch (sqoop_hive2) for this, as we do
>> not
>> > > > want
>> > > > > trunk to become unstable or introduce "breaking changes" before
>> the
>> > > > > proposed 1.4.7 release.
>> > > > >
>> > > > > Does anyone have any concerns about this?
>> > > > >
>> > > > > And in general do we have a policy about feature branches for
>> sqoop
>> > > > (like a
>> > > > > sqoop_kerberos branch, etc.)?
>> > > > >
>> > > > > Thanks,
>> > > > > Anna
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Szabolcs Vasas
>> > > Software Engineer
>> > > <http://www.cloudera.com>
>> > >
>> >
>>
>>
>>
>> --
>> Szabolcs Vasas
>> Software Engineer
>> <http://www.cloudera.com>
>>
>
>
Re: Creating feature branches
Posted by Boglarka Egyed <bo...@cloudera.com>.
Hi Attila,
You mentioned that you have a plan for releasing 1.4.7, could you please
give an update on that?
Many thanks,
Bogi
On Tue, May 16, 2017 at 10:35 AM, Szabolcs Vasas <va...@cloudera.com> wrote:
> Hi Attila,
>
> I don't have a list of JIRAs yet this was just an idea we can implement in
> the future.
>
> Szabolcs
>
> On Mon, May 15, 2017 at 6:23 PM, Attila Szabó <ma...@apache.org> wrote:
>
> > Hey Szabi:
> > Do you already have a plan ( I mean a list of JIRA issues for your first
> > feature branch(es))
> >
> > Thanks,
> > Attila
> >
> > On May 15, 2017 3:15 PM, "Szabolcs Vasas" <va...@cloudera.com> wrote:
> >
> > > Hi all,
> > >
> > > I also like the idea of creating feature branches. As far as I see we
> > > cannot create Sqoop epics on issues.apache.org so we could use
> subtasks
> > to
> > > track what do we plan to put in a feature branch.
> > >
> > > Regards,
> > > Szabolcs
> > >
> > > On Fri, May 12, 2017 at 2:15 PM, Attila Szabó <ma...@apache.org>
> wrote:
> > >
> > > > Hey Anna,
> > > >
> > > >
> > > > On my side: +1 if it helps your development efforts, and if the
> feature
> > > > branch won't be a "long living" one. (and of course you would merge
> it
> > > with
> > > > the trunk frequently not to let it diverge too much from other
> > changes).
> > > >
> > > >
> > > > Related actions (by me):
> > > >
> > > > I would like to support your efforts on this side by finalizing the
> > 1.4.7
> > > > release dates with the community soon (I'd like to send an email
> about
> > > > those efforts still today).
> > > >
> > > >
> > > > On request:
> > > >
> > > > Would you please enlist the JIRA tasks you'd like to work on related
> to
> > > > that specific feature branch (thus the whole community would be able
> to
> > > see
> > > > the scope of the features you'd working on).
> > > >
> > > >
> > > > Cheers,
> > > >
> > > > Attila
> > > >
> > > > On Fri, May 12, 2017 at 11:58 AM, Anna Szonyi <sz...@cloudera.com>
> > > wrote:
> > > >
> > > > > Hi @devs,
> > > > >
> > > > > We would like to start the preparation for upgrading to hive 2
> > (upgrade
> > > > > version, migrate off of hive cli and onto beeline, etc.).
> > > > > As we anticipate there being a few patches we were thinking it
> would
> > > make
> > > > > sense to create a feature branch (sqoop_hive2) for this, as we do
> not
> > > > want
> > > > > trunk to become unstable or introduce "breaking changes" before the
> > > > > proposed 1.4.7 release.
> > > > >
> > > > > Does anyone have any concerns about this?
> > > > >
> > > > > And in general do we have a policy about feature branches for sqoop
> > > > (like a
> > > > > sqoop_kerberos branch, etc.)?
> > > > >
> > > > > Thanks,
> > > > > Anna
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Szabolcs Vasas
> > > Software Engineer
> > > <http://www.cloudera.com>
> > >
> >
>
>
>
> --
> Szabolcs Vasas
> Software Engineer
> <http://www.cloudera.com>
>
Re: Creating feature branches
Posted by Szabolcs Vasas <va...@cloudera.com>.
Hi Attila,
I don't have a list of JIRAs yet this was just an idea we can implement in
the future.
Szabolcs
On Mon, May 15, 2017 at 6:23 PM, Attila Szabó <ma...@apache.org> wrote:
> Hey Szabi:
> Do you already have a plan ( I mean a list of JIRA issues for your first
> feature branch(es))
>
> Thanks,
> Attila
>
> On May 15, 2017 3:15 PM, "Szabolcs Vasas" <va...@cloudera.com> wrote:
>
> > Hi all,
> >
> > I also like the idea of creating feature branches. As far as I see we
> > cannot create Sqoop epics on issues.apache.org so we could use subtasks
> to
> > track what do we plan to put in a feature branch.
> >
> > Regards,
> > Szabolcs
> >
> > On Fri, May 12, 2017 at 2:15 PM, Attila Szabó <ma...@apache.org> wrote:
> >
> > > Hey Anna,
> > >
> > >
> > > On my side: +1 if it helps your development efforts, and if the feature
> > > branch won't be a "long living" one. (and of course you would merge it
> > with
> > > the trunk frequently not to let it diverge too much from other
> changes).
> > >
> > >
> > > Related actions (by me):
> > >
> > > I would like to support your efforts on this side by finalizing the
> 1.4.7
> > > release dates with the community soon (I'd like to send an email about
> > > those efforts still today).
> > >
> > >
> > > On request:
> > >
> > > Would you please enlist the JIRA tasks you'd like to work on related to
> > > that specific feature branch (thus the whole community would be able to
> > see
> > > the scope of the features you'd working on).
> > >
> > >
> > > Cheers,
> > >
> > > Attila
> > >
> > > On Fri, May 12, 2017 at 11:58 AM, Anna Szonyi <sz...@cloudera.com>
> > wrote:
> > >
> > > > Hi @devs,
> > > >
> > > > We would like to start the preparation for upgrading to hive 2
> (upgrade
> > > > version, migrate off of hive cli and onto beeline, etc.).
> > > > As we anticipate there being a few patches we were thinking it would
> > make
> > > > sense to create a feature branch (sqoop_hive2) for this, as we do not
> > > want
> > > > trunk to become unstable or introduce "breaking changes" before the
> > > > proposed 1.4.7 release.
> > > >
> > > > Does anyone have any concerns about this?
> > > >
> > > > And in general do we have a policy about feature branches for sqoop
> > > (like a
> > > > sqoop_kerberos branch, etc.)?
> > > >
> > > > Thanks,
> > > > Anna
> > > >
> > >
> >
> >
> >
> > --
> > Szabolcs Vasas
> > Software Engineer
> > <http://www.cloudera.com>
> >
>
--
Szabolcs Vasas
Software Engineer
<http://www.cloudera.com>
Re: Creating feature branches
Posted by Attila Szabó <ma...@apache.org>.
Hey Szabi:
Do you already have a plan ( I mean a list of JIRA issues for your first
feature branch(es))
Thanks,
Attila
On May 15, 2017 3:15 PM, "Szabolcs Vasas" <va...@cloudera.com> wrote:
> Hi all,
>
> I also like the idea of creating feature branches. As far as I see we
> cannot create Sqoop epics on issues.apache.org so we could use subtasks to
> track what do we plan to put in a feature branch.
>
> Regards,
> Szabolcs
>
> On Fri, May 12, 2017 at 2:15 PM, Attila Szabó <ma...@apache.org> wrote:
>
> > Hey Anna,
> >
> >
> > On my side: +1 if it helps your development efforts, and if the feature
> > branch won't be a "long living" one. (and of course you would merge it
> with
> > the trunk frequently not to let it diverge too much from other changes).
> >
> >
> > Related actions (by me):
> >
> > I would like to support your efforts on this side by finalizing the 1.4.7
> > release dates with the community soon (I'd like to send an email about
> > those efforts still today).
> >
> >
> > On request:
> >
> > Would you please enlist the JIRA tasks you'd like to work on related to
> > that specific feature branch (thus the whole community would be able to
> see
> > the scope of the features you'd working on).
> >
> >
> > Cheers,
> >
> > Attila
> >
> > On Fri, May 12, 2017 at 11:58 AM, Anna Szonyi <sz...@cloudera.com>
> wrote:
> >
> > > Hi @devs,
> > >
> > > We would like to start the preparation for upgrading to hive 2 (upgrade
> > > version, migrate off of hive cli and onto beeline, etc.).
> > > As we anticipate there being a few patches we were thinking it would
> make
> > > sense to create a feature branch (sqoop_hive2) for this, as we do not
> > want
> > > trunk to become unstable or introduce "breaking changes" before the
> > > proposed 1.4.7 release.
> > >
> > > Does anyone have any concerns about this?
> > >
> > > And in general do we have a policy about feature branches for sqoop
> > (like a
> > > sqoop_kerberos branch, etc.)?
> > >
> > > Thanks,
> > > Anna
> > >
> >
>
>
>
> --
> Szabolcs Vasas
> Software Engineer
> <http://www.cloudera.com>
>
Re: Creating feature branches
Posted by Szabolcs Vasas <va...@cloudera.com>.
Hi all,
I also like the idea of creating feature branches. As far as I see we
cannot create Sqoop epics on issues.apache.org so we could use subtasks to
track what do we plan to put in a feature branch.
Regards,
Szabolcs
On Fri, May 12, 2017 at 2:15 PM, Attila Szabó <ma...@apache.org> wrote:
> Hey Anna,
>
>
> On my side: +1 if it helps your development efforts, and if the feature
> branch won't be a "long living" one. (and of course you would merge it with
> the trunk frequently not to let it diverge too much from other changes).
>
>
> Related actions (by me):
>
> I would like to support your efforts on this side by finalizing the 1.4.7
> release dates with the community soon (I'd like to send an email about
> those efforts still today).
>
>
> On request:
>
> Would you please enlist the JIRA tasks you'd like to work on related to
> that specific feature branch (thus the whole community would be able to see
> the scope of the features you'd working on).
>
>
> Cheers,
>
> Attila
>
> On Fri, May 12, 2017 at 11:58 AM, Anna Szonyi <sz...@cloudera.com> wrote:
>
> > Hi @devs,
> >
> > We would like to start the preparation for upgrading to hive 2 (upgrade
> > version, migrate off of hive cli and onto beeline, etc.).
> > As we anticipate there being a few patches we were thinking it would make
> > sense to create a feature branch (sqoop_hive2) for this, as we do not
> want
> > trunk to become unstable or introduce "breaking changes" before the
> > proposed 1.4.7 release.
> >
> > Does anyone have any concerns about this?
> >
> > And in general do we have a policy about feature branches for sqoop
> (like a
> > sqoop_kerberos branch, etc.)?
> >
> > Thanks,
> > Anna
> >
>
--
Szabolcs Vasas
Software Engineer
<http://www.cloudera.com>
Re: Creating feature branches
Posted by Attila Szabó <ma...@apache.org>.
Hey Anna,
On my side: +1 if it helps your development efforts, and if the feature
branch won't be a "long living" one. (and of course you would merge it with
the trunk frequently not to let it diverge too much from other changes).
Related actions (by me):
I would like to support your efforts on this side by finalizing the 1.4.7
release dates with the community soon (I'd like to send an email about
those efforts still today).
On request:
Would you please enlist the JIRA tasks you'd like to work on related to
that specific feature branch (thus the whole community would be able to see
the scope of the features you'd working on).
Cheers,
Attila
On Fri, May 12, 2017 at 11:58 AM, Anna Szonyi <sz...@cloudera.com> wrote:
> Hi @devs,
>
> We would like to start the preparation for upgrading to hive 2 (upgrade
> version, migrate off of hive cli and onto beeline, etc.).
> As we anticipate there being a few patches we were thinking it would make
> sense to create a feature branch (sqoop_hive2) for this, as we do not want
> trunk to become unstable or introduce "breaking changes" before the
> proposed 1.4.7 release.
>
> Does anyone have any concerns about this?
>
> And in general do we have a policy about feature branches for sqoop (like a
> sqoop_kerberos branch, etc.)?
>
> Thanks,
> Anna
>