Re: New release branch 2.0.0

2017-11-28 Thread Kalyan Kumar Kalvagadda 
Colm,

that is the issue. I will update the wiki accordingly.

-Kalyan

On Tue, Nov 28, 2017 at 11:11 AM, Colm O hEigeartaigh 
wrote:

> Hmm I'm not sure if that's correct, it should look more like:
>
> 
>   
>
> 
>apache.releases.https
>coheigea
>...
> 
>
> 
>apache.staging.https
>coheigea
>...
> 
>   
> 
>
> On Tue, Nov 28, 2017 at 5:02 PM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > Colm,
> >
> > This the the complete content of my settings.xml.
> >>
> >> 
> >>
> >>   apache.staging.https
> >>
> >>   kalyan
> >>
> >>   *
> >>
> >>apache.releases.https
> >>
> >>   kalyan
> >>
> >>   *
> >>
> >>  
> >>
> >>
> >
> > I'm running below command.
> >
> >> mvn -s ~/.m2/settings.xml clean deploy -Psign-artifacts
> >
> >
> > I still observe the same issue.
> >
> > -Kalyan
> >
> > On Tue, Nov 28, 2017 at 10:46 AM, Colm O hEigeartaigh <
> cohei...@apache.org
> > > wrote:
> >
> >> I think it should be "apache.releases.https" based on the error message
> >> below. I have both in my local settings.xml, so you could try adding
> both
> >> in!
> >>
> >> Colm.
> >>
> >> On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
> >> wrote:
> >>
> >> > I have the same issue.
> >> >
> >> > Colm, the wiki mentioned "apache.staging.https". is that the correct
> >> one?
> >> >
> >> > On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh <
> >> cohei...@apache.org
> >> > > wrote:
> >> >
> >> >> Have you got a "apache.releases.https" server defined in your maven
> >> >> settings.xml, with a corresponding username + password?
> >> >>
> >> >> Colm.
> >> >>
> >> >> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
> >> >> kkal...@cloudera.com> wrote:
> >> >>
> >> >> > I'm observing error while deploying the artifacts in maven
> >> repository.
> >> >> > Looks like I don't have permission to do it.
> >> >> >
> >> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> >> >> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project
> >> sentry:
> >> >> > > Failed to deploy artifacts: Could not transfer artifact
> >> >> > > org.apache.sentry:sentry:pom:2.0.0 from/to
> apache.releases.https (
> >> >> > > https://repository.apache.org/service/local/staging/deploy/
> maven2
> >> ):
> >> >> > > Failed to transfer file: https://repository.apache.org/
> >> >> > > service/local/staging/deploy/maven2/org/apache/sentry/
> >> >> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> >> >> > > *Unauthorized*. -> [Help 1]
> >> >> > >
> >> >> >
> >> >> >
> >> >> > Does any one know if I need some permissions to deploy?
> >> >> >
> >> >> > -Kalyan
> >> >> >
> >> >> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> >> >> > kkal...@cloudera.com> wrote:
> >> >> >
> >> >> > > Sure, I will change the branch to sentry-2.0
> >> >> > >
> >> >> > > Thanks,
> >> >> > > Kalyan
> >> >> > >
> >> >> > > -Kalyan
> >> >> > >
> >> >> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
> >> >> sergio.p...@cloudera.com>
> >> >> > > wrote:
> >> >> > >
> >> >> > >> That's old Kalyan. Why do you propose bringing back the old
> >> approach?
> >> >> > The
> >> >> > >> new approach is used by other Apache components where bugfix
> >> releases
> >> >> > are
> >> >> > >> only tags. This reduces the release process and steps of bugfix
> >> >> > releases.
> >> >> > >>
> >> >> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> >> >> > >> kkal...@cloudera.com> wrote:
> >> >> > >>
> >> >> > >> > Sergio,
> >> >> > >> >
> >> >> > >> > If you look at all the previous branches they are followed
> >> >> convention
> >> >> > >> > sentry-major.minor.patch. I tried to be in-line with them.
> >> >> > >> >
> >> >> > >> > -Kalyan
> >> >> > >> >
> >> >> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> >> >> > sergio.p...@cloudera.com>
> >> >> > >> > wrote:
> >> >> > >> >
> >> >> > >> > > Great, thanks Kalyan.
> >> >> > >> > >
> >> >> > >> > > Btw, the branch should be named branch-2.0 as the Wiki
> >> suggests
> >> >> (git
> >> >> > >> > > checkout -b branch-1.8). It is better to name a branch this
> >> way
> >> >> so
> >> >> > we
> >> >> > >> can
> >> >> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> >> >> > >> > >
> >> >> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> >> >> > >> > > kkal...@cloudera.com> wrote:
> >> >> > >> > >
> >> >> > >> > > > I've just created new release branch for upcoming 2.0.0
> >> >> release.
> >> >> > >> Please
> >> >> > >> > > > continue committing to master branch as usual.
> >> >> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> >> >> > >> > > >
> >> >> > >> > > > -Kalyan
> >> >> > >> > > >
> >> >> > >> > >
> >> >> > >> >
> >> >> > >>
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Colm O hEigeartaigh
> >> >>
> >> >> Talend Community Coder
> >> >>

Re: New release branch 2.0.0

2017-11-28 Thread Colm O hEigeartaigh 
Hmm I'm not sure if that's correct, it should look more like:


  


   apache.releases.https
   coheigea
   ...



   apache.staging.https
   coheigea
   ...

  


On Tue, Nov 28, 2017 at 5:02 PM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> Colm,
>
> This the the complete content of my settings.xml.
>>
>> 
>>
>>   apache.staging.https
>>
>>   kalyan
>>
>>   *
>>
>>apache.releases.https
>>
>>   kalyan
>>
>>   *
>>
>>  
>>
>>
>
> I'm running below command.
>
>> mvn -s ~/.m2/settings.xml clean deploy -Psign-artifacts
>
>
> I still observe the same issue.
>
> -Kalyan
>
> On Tue, Nov 28, 2017 at 10:46 AM, Colm O hEigeartaigh  > wrote:
>
>> I think it should be "apache.releases.https" based on the error message
>> below. I have both in my local settings.xml, so you could try adding both
>> in!
>>
>> Colm.
>>
>> On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
>> wrote:
>>
>> > I have the same issue.
>> >
>> > Colm, the wiki mentioned "apache.staging.https". is that the correct
>> one?
>> >
>> > On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh <
>> cohei...@apache.org
>> > > wrote:
>> >
>> >> Have you got a "apache.releases.https" server defined in your maven
>> >> settings.xml, with a corresponding username + password?
>> >>
>> >> Colm.
>> >>
>> >> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
>> >> kkal...@cloudera.com> wrote:
>> >>
>> >> > I'm observing error while deploying the artifacts in maven
>> repository.
>> >> > Looks like I don't have permission to do it.
>> >> >
>> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
>> >> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project
>> sentry:
>> >> > > Failed to deploy artifacts: Could not transfer artifact
>> >> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
>> >> > > https://repository.apache.org/service/local/staging/deploy/maven2
>> ):
>> >> > > Failed to transfer file: https://repository.apache.org/
>> >> > > service/local/staging/deploy/maven2/org/apache/sentry/
>> >> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
>> >> > > *Unauthorized*. -> [Help 1]
>> >> > >
>> >> >
>> >> >
>> >> > Does any one know if I need some permissions to deploy?
>> >> >
>> >> > -Kalyan
>> >> >
>> >> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
>> >> > kkal...@cloudera.com> wrote:
>> >> >
>> >> > > Sure, I will change the branch to sentry-2.0
>> >> > >
>> >> > > Thanks,
>> >> > > Kalyan
>> >> > >
>> >> > > -Kalyan
>> >> > >
>> >> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
>> >> sergio.p...@cloudera.com>
>> >> > > wrote:
>> >> > >
>> >> > >> That's old Kalyan. Why do you propose bringing back the old
>> approach?
>> >> > The
>> >> > >> new approach is used by other Apache components where bugfix
>> releases
>> >> > are
>> >> > >> only tags. This reduces the release process and steps of bugfix
>> >> > releases.
>> >> > >>
>> >> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
>> >> > >> kkal...@cloudera.com> wrote:
>> >> > >>
>> >> > >> > Sergio,
>> >> > >> >
>> >> > >> > If you look at all the previous branches they are followed
>> >> convention
>> >> > >> > sentry-major.minor.patch. I tried to be in-line with them.
>> >> > >> >
>> >> > >> > -Kalyan
>> >> > >> >
>> >> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
>> >> > sergio.p...@cloudera.com>
>> >> > >> > wrote:
>> >> > >> >
>> >> > >> > > Great, thanks Kalyan.
>> >> > >> > >
>> >> > >> > > Btw, the branch should be named branch-2.0 as the Wiki
>> suggests
>> >> (git
>> >> > >> > > checkout -b branch-1.8). It is better to name a branch this
>> way
>> >> so
>> >> > we
>> >> > >> can
>> >> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
>> >> > >> > >
>> >> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
>> >> > >> > > kkal...@cloudera.com> wrote:
>> >> > >> > >
>> >> > >> > > > I've just created new release branch for upcoming 2.0.0
>> >> release.
>> >> > >> Please
>> >> > >> > > > continue committing to master branch as usual.
>> >> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
>> >> > >> > > >
>> >> > >> > > > -Kalyan
>> >> > >> > > >
>> >> > >> > >
>> >> > >> >
>> >> > >>
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Colm O hEigeartaigh
>> >>
>> >> Talend Community Coder
>> >> http://coders.talend.com
>> >>
>> >
>> >
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: New release branch 2.0.0

2017-11-28 Thread Kalyan Kumar Kalvagadda 
Colm,

This the the complete content of my settings.xml.
>
> 
>
>   apache.staging.https
>
>   kalyan
>
>   *
>
>apache.releases.https
>
>   kalyan
>
>   *
>
>  
>
>

I'm running below command.

> mvn -s ~/.m2/settings.xml clean deploy -Psign-artifacts


I still observe the same issue.

-Kalyan

On Tue, Nov 28, 2017 at 10:46 AM, Colm O hEigeartaigh 
wrote:

> I think it should be "apache.releases.https" based on the error message
> below. I have both in my local settings.xml, so you could try adding both
> in!
>
> Colm.
>
> On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
> wrote:
>
> > I have the same issue.
> >
> > Colm, the wiki mentioned "apache.staging.https". is that the correct one?
> >
> > On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh <
> cohei...@apache.org
> > > wrote:
> >
> >> Have you got a "apache.releases.https" server defined in your maven
> >> settings.xml, with a corresponding username + password?
> >>
> >> Colm.
> >>
> >> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
> >> kkal...@cloudera.com> wrote:
> >>
> >> > I'm observing error while deploying the artifacts in maven repository.
> >> > Looks like I don't have permission to do it.
> >> >
> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> >> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project
> sentry:
> >> > > Failed to deploy artifacts: Could not transfer artifact
> >> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> >> > > https://repository.apache.org/service/local/staging/deploy/maven2):
> >> > > Failed to transfer file: https://repository.apache.org/
> >> > > service/local/staging/deploy/maven2/org/apache/sentry/
> >> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> >> > > *Unauthorized*. -> [Help 1]
> >> > >
> >> >
> >> >
> >> > Does any one know if I need some permissions to deploy?
> >> >
> >> > -Kalyan
> >> >
> >> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> >> > kkal...@cloudera.com> wrote:
> >> >
> >> > > Sure, I will change the branch to sentry-2.0
> >> > >
> >> > > Thanks,
> >> > > Kalyan
> >> > >
> >> > > -Kalyan
> >> > >
> >> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
> >> sergio.p...@cloudera.com>
> >> > > wrote:
> >> > >
> >> > >> That's old Kalyan. Why do you propose bringing back the old
> approach?
> >> > The
> >> > >> new approach is used by other Apache components where bugfix
> releases
> >> > are
> >> > >> only tags. This reduces the release process and steps of bugfix
> >> > releases.
> >> > >>
> >> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> >> > >> kkal...@cloudera.com> wrote:
> >> > >>
> >> > >> > Sergio,
> >> > >> >
> >> > >> > If you look at all the previous branches they are followed
> >> convention
> >> > >> > sentry-major.minor.patch. I tried to be in-line with them.
> >> > >> >
> >> > >> > -Kalyan
> >> > >> >
> >> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> >> > sergio.p...@cloudera.com>
> >> > >> > wrote:
> >> > >> >
> >> > >> > > Great, thanks Kalyan.
> >> > >> > >
> >> > >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests
> >> (git
> >> > >> > > checkout -b branch-1.8). It is better to name a branch this way
> >> so
> >> > we
> >> > >> can
> >> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> >> > >> > >
> >> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> >> > >> > > kkal...@cloudera.com> wrote:
> >> > >> > >
> >> > >> > > > I've just created new release branch for upcoming 2.0.0
> >> release.
> >> > >> Please
> >> > >> > > > continue committing to master branch as usual.
> >> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> >> > >> > > >
> >> > >> > > > -Kalyan
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Colm O hEigeartaigh
> >>
> >> Talend Community Coder
> >> http://coders.talend.com
> >>
> >
> >
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Re: New release branch 2.0.0

2017-11-28 Thread Colm O hEigeartaigh 
I think it should be "apache.releases.https" based on the error message
below. I have both in my local settings.xml, so you could try adding both
in!

Colm.

On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena 
wrote:

> I have the same issue.
>
> Colm, the wiki mentioned "apache.staging.https". is that the correct one?
>
> On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh  > wrote:
>
>> Have you got a "apache.releases.https" server defined in your maven
>> settings.xml, with a corresponding username + password?
>>
>> Colm.
>>
>> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
>> kkal...@cloudera.com> wrote:
>>
>> > I'm observing error while deploying the artifacts in maven repository.
>> > Looks like I don't have permission to do it.
>> >
>> > [ERROR] Failed to execute goal org.apache.maven.plugins:
>> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
>> > > Failed to deploy artifacts: Could not transfer artifact
>> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
>> > > https://repository.apache.org/service/local/staging/deploy/maven2):
>> > > Failed to transfer file: https://repository.apache.org/
>> > > service/local/staging/deploy/maven2/org/apache/sentry/
>> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
>> > > *Unauthorized*. -> [Help 1]
>> > >
>> >
>> >
>> > Does any one know if I need some permissions to deploy?
>> >
>> > -Kalyan
>> >
>> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
>> > kkal...@cloudera.com> wrote:
>> >
>> > > Sure, I will change the branch to sentry-2.0
>> > >
>> > > Thanks,
>> > > Kalyan
>> > >
>> > > -Kalyan
>> > >
>> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
>> sergio.p...@cloudera.com>
>> > > wrote:
>> > >
>> > >> That's old Kalyan. Why do you propose bringing back the old approach?
>> > The
>> > >> new approach is used by other Apache components where bugfix releases
>> > are
>> > >> only tags. This reduces the release process and steps of bugfix
>> > releases.
>> > >>
>> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
>> > >> kkal...@cloudera.com> wrote:
>> > >>
>> > >> > Sergio,
>> > >> >
>> > >> > If you look at all the previous branches they are followed
>> convention
>> > >> > sentry-major.minor.patch. I tried to be in-line with them.
>> > >> >
>> > >> > -Kalyan
>> > >> >
>> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
>> > sergio.p...@cloudera.com>
>> > >> > wrote:
>> > >> >
>> > >> > > Great, thanks Kalyan.
>> > >> > >
>> > >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests
>> (git
>> > >> > > checkout -b branch-1.8). It is better to name a branch this way
>> so
>> > we
>> > >> can
>> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
>> > >> > >
>> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
>> > >> > > kkal...@cloudera.com> wrote:
>> > >> > >
>> > >> > > > I've just created new release branch for upcoming 2.0.0
>> release.
>> > >> Please
>> > >> > > > continue committing to master branch as usual.
>> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
>> > >> > > >
>> > >> > > > -Kalyan
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: New release branch 2.0.0

2017-11-28 Thread Sergio Pena 
I have the same issue.

Colm, the wiki mentioned "apache.staging.https". is that the correct one?

On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh 
wrote:

> Have you got a "apache.releases.https" server defined in your maven
> settings.xml, with a corresponding username + password?
>
> Colm.
>
> On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > I'm observing error while deploying the artifacts in maven repository.
> > Looks like I don't have permission to do it.
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> > > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
> > > Failed to deploy artifacts: Could not transfer artifact
> > > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> > > https://repository.apache.org/service/local/staging/deploy/maven2):
> > > Failed to transfer file: https://repository.apache.org/
> > > service/local/staging/deploy/maven2/org/apache/sentry/
> > > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> > > *Unauthorized*. -> [Help 1]
> > >
> >
> >
> > Does any one know if I need some permissions to deploy?
> >
> > -Kalyan
> >
> > On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> > kkal...@cloudera.com> wrote:
> >
> > > Sure, I will change the branch to sentry-2.0
> > >
> > > Thanks,
> > > Kalyan
> > >
> > > -Kalyan
> > >
> > > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena <
> sergio.p...@cloudera.com>
> > > wrote:
> > >
> > >> That's old Kalyan. Why do you propose bringing back the old approach?
> > The
> > >> new approach is used by other Apache components where bugfix releases
> > are
> > >> only tags. This reduces the release process and steps of bugfix
> > releases.
> > >>
> > >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> > >> kkal...@cloudera.com> wrote:
> > >>
> > >> > Sergio,
> > >> >
> > >> > If you look at all the previous branches they are followed
> convention
> > >> > sentry-major.minor.patch. I tried to be in-line with them.
> > >> >
> > >> > -Kalyan
> > >> >
> > >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> > sergio.p...@cloudera.com>
> > >> > wrote:
> > >> >
> > >> > > Great, thanks Kalyan.
> > >> > >
> > >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests
> (git
> > >> > > checkout -b branch-1.8). It is better to name a branch this way so
> > we
> > >> can
> > >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> > >> > >
> > >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> > >> > > kkal...@cloudera.com> wrote:
> > >> > >
> > >> > > > I've just created new release branch for upcoming 2.0.0 release.
> > >> Please
> > >> > > > continue committing to master branch as usual.
> > >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> > >> > > >
> > >> > > > -Kalyan
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Re: New release branch 2.0.0

2017-11-28 Thread Colm O hEigeartaigh 
Have you got a "apache.releases.https" server defined in your maven
settings.xml, with a corresponding username + password?

Colm.

On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> I'm observing error while deploying the artifacts in maven repository.
> Looks like I don't have permission to do it.
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
> > Failed to deploy artifacts: Could not transfer artifact
> > org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> > https://repository.apache.org/service/local/staging/deploy/maven2):
> > Failed to transfer file: https://repository.apache.org/
> > service/local/staging/deploy/maven2/org/apache/sentry/
> > sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> > *Unauthorized*. -> [Help 1]
> >
>
>
> Does any one know if I need some permissions to deploy?
>
> -Kalyan
>
> On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > Sure, I will change the branch to sentry-2.0
> >
> > Thanks,
> > Kalyan
> >
> > -Kalyan
> >
> > On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena 
> > wrote:
> >
> >> That's old Kalyan. Why do you propose bringing back the old approach?
> The
> >> new approach is used by other Apache components where bugfix releases
> are
> >> only tags. This reduces the release process and steps of bugfix
> releases.
> >>
> >> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> >> kkal...@cloudera.com> wrote:
> >>
> >> > Sergio,
> >> >
> >> > If you look at all the previous branches they are followed convention
> >> > sentry-major.minor.patch. I tried to be in-line with them.
> >> >
> >> > -Kalyan
> >> >
> >> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena <
> sergio.p...@cloudera.com>
> >> > wrote:
> >> >
> >> > > Great, thanks Kalyan.
> >> > >
> >> > > Btw, the branch should be named branch-2.0 as the Wiki suggests (git
> >> > > checkout -b branch-1.8). It is better to name a branch this way so
> we
> >> can
> >> > > commit bugfixes on it for future 2.0.x bugfix releases.
> >> > >
> >> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> >> > > kkal...@cloudera.com> wrote:
> >> > >
> >> > > > I've just created new release branch for upcoming 2.0.0 release.
> >> Please
> >> > > > continue committing to master branch as usual.
> >> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> >> > > >
> >> > > > -Kalyan
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: New release branch 2.0.0

2017-11-28 Thread Kalyan Kumar Kalvagadda 
I'm observing error while deploying the artifacts in maven repository.
Looks like I don't have permission to do it.

[ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry:
> Failed to deploy artifacts: Could not transfer artifact
> org.apache.sentry:sentry:pom:2.0.0 from/to apache.releases.https (
> https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file: https://repository.apache.org/
> service/local/staging/deploy/maven2/org/apache/sentry/
> sentry/2.0.0/sentry-2.0.0.pom. Return code is: 401, ReasonPhrase:
> *Unauthorized*. -> [Help 1]
>


Does any one know if I need some permissions to deploy?

-Kalyan

On Mon, Nov 27, 2017 at 11:10 AM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> Sure, I will change the branch to sentry-2.0
>
> Thanks,
> Kalyan
>
> -Kalyan
>
> On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena 
> wrote:
>
>> That's old Kalyan. Why do you propose bringing back the old approach? The
>> new approach is used by other Apache components where bugfix releases are
>> only tags. This reduces the release process and steps of bugfix releases.
>>
>> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
>> kkal...@cloudera.com> wrote:
>>
>> > Sergio,
>> >
>> > If you look at all the previous branches they are followed convention
>> > sentry-major.minor.patch. I tried to be in-line with them.
>> >
>> > -Kalyan
>> >
>> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena 
>> > wrote:
>> >
>> > > Great, thanks Kalyan.
>> > >
>> > > Btw, the branch should be named branch-2.0 as the Wiki suggests (git
>> > > checkout -b branch-1.8). It is better to name a branch this way so we
>> can
>> > > commit bugfixes on it for future 2.0.x bugfix releases.
>> > >
>> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
>> > > kkal...@cloudera.com> wrote:
>> > >
>> > > > I've just created new release branch for upcoming 2.0.0 release.
>> Please
>> > > > continue committing to master branch as usual.
>> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
>> > > >
>> > > > -Kalyan
>> > > >
>> > >
>> >
>>
>
>

Re: New release branch 2.0.0

2017-11-27 Thread Kalyan Kumar Kalvagadda 
Sure, I will change the branch to sentry-2.0

Thanks,
Kalyan

-Kalyan

On Mon, Nov 27, 2017 at 10:54 AM, Sergio Pena 
wrote:

> That's old Kalyan. Why do you propose bringing back the old approach? The
> new approach is used by other Apache components where bugfix releases are
> only tags. This reduces the release process and steps of bugfix releases.
>
> On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > Sergio,
> >
> > If you look at all the previous branches they are followed convention
> > sentry-major.minor.patch. I tried to be in-line with them.
> >
> > -Kalyan
> >
> > On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena 
> > wrote:
> >
> > > Great, thanks Kalyan.
> > >
> > > Btw, the branch should be named branch-2.0 as the Wiki suggests (git
> > > checkout -b branch-1.8). It is better to name a branch this way so we
> can
> > > commit bugfixes on it for future 2.0.x bugfix releases.
> > >
> > > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> > > kkal...@cloudera.com> wrote:
> > >
> > > > I've just created new release branch for upcoming 2.0.0 release.
> Please
> > > > continue committing to master branch as usual.
> > > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> > > >
> > > > -Kalyan
> > > >
> > >
> >
>

Re: New release branch 2.0.0

2017-11-27 Thread Sergio Pena 
That's old Kalyan. Why do you propose bringing back the old approach? The
new approach is used by other Apache components where bugfix releases are
only tags. This reduces the release process and steps of bugfix releases.

On Mon, Nov 27, 2017 at 10:36 AM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> Sergio,
>
> If you look at all the previous branches they are followed convention
> sentry-major.minor.patch. I tried to be in-line with them.
>
> -Kalyan
>
> On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena 
> wrote:
>
> > Great, thanks Kalyan.
> >
> > Btw, the branch should be named branch-2.0 as the Wiki suggests (git
> > checkout -b branch-1.8). It is better to name a branch this way so we can
> > commit bugfixes on it for future 2.0.x bugfix releases.
> >
> > On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> > kkal...@cloudera.com> wrote:
> >
> > > I've just created new release branch for upcoming 2.0.0 release. Please
> > > continue committing to master branch as usual.
> > > I'll cherry-pick commits to branch-2.0.0 on need basis.
> > >
> > > -Kalyan
> > >
> >
>

Re: New release branch 2.0.0

2017-11-27 Thread Kalyan Kumar Kalvagadda 
Sergio,

If you look at all the previous branches they are followed convention
sentry-major.minor.patch. I tried to be in-line with them.

-Kalyan

On Mon, Nov 27, 2017 at 9:35 AM, Sergio Pena 
wrote:

> Great, thanks Kalyan.
>
> Btw, the branch should be named branch-2.0 as the Wiki suggests (git
> checkout -b branch-1.8). It is better to name a branch this way so we can
> commit bugfixes on it for future 2.0.x bugfix releases.
>
> On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
> kkal...@cloudera.com> wrote:
>
> > I've just created new release branch for upcoming 2.0.0 release. Please
> > continue committing to master branch as usual.
> > I'll cherry-pick commits to branch-2.0.0 on need basis.
> >
> > -Kalyan
> >
>

Re: New release branch 2.0.0

2017-11-27 Thread Sergio Pena 
Great, thanks Kalyan.

Btw, the branch should be named branch-2.0 as the Wiki suggests (git
checkout -b branch-1.8). It is better to name a branch this way so we can
commit bugfixes on it for future 2.0.x bugfix releases.

On Mon, Nov 27, 2017 at 8:19 AM, Kalyan Kumar Kalvagadda <
kkal...@cloudera.com> wrote:

> I've just created new release branch for upcoming 2.0.0 release. Please
> continue committing to master branch as usual.
> I'll cherry-pick commits to branch-2.0.0 on need basis.
>
> -Kalyan
>