You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by Anatole Tresch <at...@gmail.com> on 2015/08/04 12:33:16 UTC
Release Staging
Hi John/all
I was successful in uploading the release to sonatype for staging.
Unfortunately I (UID: anatole) was not able to access Nexus. I commented on
the INFRA ticket on this.
Can you check, if you have access to https://oss.sonatype.org ?
Or I am doing something wrong here? The process of staging basically is
nothing new, since I did similar things with the money JSR already, so once
I would be able to login we could continue with the release/voting
process...
Anatole
--
*Anatole Tresch*
Java Engineer & Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
<http://javaremarkables.blogspot.ch/>*
*Google: atsticksMobile +41-76 344 62 79*
Re: Release Staging
Posted by "John D. Ament" <jo...@apache.org>.
BTW, since we're using maven for the release, all of the steps from
deltaspike apply to us.
http://deltaspike.apache.org/steps_for_a_release.html
So we can reuse that info here.
On Tue, Aug 4, 2015 at 6:55 AM John D. Ament <jo...@apache.org> wrote:
> Sorry, "Close the Repo" not "Promote"
>
>
> On Tue, Aug 4, 2015 at 6:47 AM John D. Ament <jo...@apache.org>
> wrote:
>
>> Hi Anatole,
>>
>> So you're not going to push to oss.sonatype.org at this point (we need
>> to vote on the artifacts before the release goes out the door)
>>
>> If you login here https://repository.apache.org/#stagingRepositories
>> using your regulard apache username/password, you should see the staging
>> repo you created. If you click on promote you should get a URL generated
>> that is accessible to other and have the release artifacts we're voting on.
>>
>> The URL should end up being
>> https://repository.apache.org/content/repositories/orgapachetamaya-1001/
>>
>> The -src.zip/-src.tar.gz are what we vote on.
>>
>> John
>>
>>
>> On Tue, Aug 4, 2015 at 6:34 AM Anatole Tresch <at...@gmail.com> wrote:
>>
>>> Hi John/all
>>>
>>> I was successful in uploading the release to sonatype for staging.
>>> Unfortunately I (UID: anatole) was not able to access Nexus. I commented
>>> on
>>> the INFRA ticket on this.
>>> Can you check, if you have access to https://oss.sonatype.org ?
>>>
>>> Or I am doing something wrong here? The process of staging basically is
>>> nothing new, since I did similar things with the money JSR already, so
>>> once
>>> I would be able to login we could continue with the release/voting
>>> process...
>>>
>>> Anatole
>>>
>>>
>>>
>>> --
>>> *Anatole Tresch*
>>> Java Engineer & Architect, JSR Spec Lead
>>> Glärnischweg 10
>>> CH - 8620 Wetzikon
>>>
>>> *Switzerland, Europe Zurich, GMT+1*
>>> *Twitter: @atsticks*
>>> *Blogs: **http://javaremarkables.blogspot.ch/
>>> <http://javaremarkables.blogspot.ch/>*
>>>
>>> *Google: atsticksMobile +41-76 344 62 79*
>>>
>>
Re: Release Staging
Posted by "John D. Ament" <jo...@apache.org>.
Sorry, "Close the Repo" not "Promote"
On Tue, Aug 4, 2015 at 6:47 AM John D. Ament <jo...@apache.org> wrote:
> Hi Anatole,
>
> So you're not going to push to oss.sonatype.org at this point (we need to
> vote on the artifacts before the release goes out the door)
>
> If you login here https://repository.apache.org/#stagingRepositories
> using your regulard apache username/password, you should see the staging
> repo you created. If you click on promote you should get a URL generated
> that is accessible to other and have the release artifacts we're voting on.
>
> The URL should end up being
> https://repository.apache.org/content/repositories/orgapachetamaya-1001/
>
> The -src.zip/-src.tar.gz are what we vote on.
>
> John
>
>
> On Tue, Aug 4, 2015 at 6:34 AM Anatole Tresch <at...@gmail.com> wrote:
>
>> Hi John/all
>>
>> I was successful in uploading the release to sonatype for staging.
>> Unfortunately I (UID: anatole) was not able to access Nexus. I commented
>> on
>> the INFRA ticket on this.
>> Can you check, if you have access to https://oss.sonatype.org ?
>>
>> Or I am doing something wrong here? The process of staging basically is
>> nothing new, since I did similar things with the money JSR already, so
>> once
>> I would be able to login we could continue with the release/voting
>> process...
>>
>> Anatole
>>
>>
>>
>> --
>> *Anatole Tresch*
>> Java Engineer & Architect, JSR Spec Lead
>> Glärnischweg 10
>> CH - 8620 Wetzikon
>>
>> *Switzerland, Europe Zurich, GMT+1*
>> *Twitter: @atsticks*
>> *Blogs: **http://javaremarkables.blogspot.ch/
>> <http://javaremarkables.blogspot.ch/>*
>>
>> *Google: atsticksMobile +41-76 344 62 79*
>>
>
Re: Release Staging
Posted by "John D. Ament" <jo...@apache.org>.
Hi Anatole,
So you're not going to push to oss.sonatype.org at this point (we need to
vote on the artifacts before the release goes out the door)
If you login here https://repository.apache.org/#stagingRepositories
using your regulard apache username/password, you should see the staging
repo you created. If you click on promote you should get a URL generated
that is accessible to other and have the release artifacts we're voting on.
The URL should end up being
https://repository.apache.org/content/repositories/orgapachetamaya-1001/
The -src.zip/-src.tar.gz are what we vote on.
John
On Tue, Aug 4, 2015 at 6:34 AM Anatole Tresch <at...@gmail.com> wrote:
> Hi John/all
>
> I was successful in uploading the release to sonatype for staging.
> Unfortunately I (UID: anatole) was not able to access Nexus. I commented on
> the INFRA ticket on this.
> Can you check, if you have access to https://oss.sonatype.org ?
>
> Or I am doing something wrong here? The process of staging basically is
> nothing new, since I did similar things with the money JSR already, so once
> I would be able to login we could continue with the release/voting
> process...
>
> Anatole
>
>
>
> --
> *Anatole Tresch*
> Java Engineer & Architect, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
>
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter: @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/
> <http://javaremarkables.blogspot.ch/>*
>
> *Google: atsticksMobile +41-76 344 62 79*
>
Re: Release Staging
Posted by "John D. Ament" <jo...@apache.org>.
Yay! It closed!
https://repository.apache.org/content/repositories/orgapachetamaya-1001/
We now have a staged release that can be voted upon.
John
On Tue, Aug 4, 2015 at 7:59 AM John D. Ament <jo...@apache.org> wrote:
> Agreed, it can be confusing. Looks like the only step left is closing the
> repo.
>
> John
>
>
> On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <at...@gmail.com> wrote:
>
>> I just did what is described here:
>> http://www.apache.org/dev/publishing-maven-artifacts.html
>> <http://www.apache.org/dev/publishing-maven-artifacts.html>
>>
>> or, more especially here:
>>
>> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
>>
>> Then:
>> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
>>
>> And finally:
>>
>> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
>>
>> So *section 4* here is completely misleading IMO:
>> 4 - STAGE THE RELEASE FOR A VOTE¶
>> <
>> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
>> >
>>
>> mvn release:perform
>>
>> The release will automatically be inserted into a temporary staging
>> repository for you. See the Nexus staging documentation
>> <http://www.sonatype.com/books/nexus-book/reference/staging.html> for
>> full
>> details.
>>
>> Now you must close the staging repository to indicate to Nexus that the
>> build is done and to make the artifacts available. Follow the steps
>> inClosing
>> the Staged Repository
>> <http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage>
>> to
>> close your new repository, *this will allow your community to VOTE on the
>> staged atrifacts*.
>>
>> But fair enough, now things look clearer again ;)
>>
>> Thanks
>> Anatole
>>
>>
>> 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>>
>> > You should stage on apache then it will get sync-ed on central no?
>> > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a écrit :
>> >
>> > > Hi John/all
>> > >
>> > > I was successful in uploading the release to sonatype for staging.
>> > > Unfortunately I (UID: anatole) was not able to access Nexus. I
>> commented
>> > on
>> > > the INFRA ticket on this.
>> > > Can you check, if you have access to https://oss.sonatype.org ?
>> > >
>> > > Or I am doing something wrong here? The process of staging basically
>> is
>> > > nothing new, since I did similar things with the money JSR already, so
>> > once
>> > > I would be able to login we could continue with the release/voting
>> > > process...
>> > >
>> > > Anatole
>> > >
>> > >
>> > >
>> > > --
>> > > *Anatole Tresch*
>> > > Java Engineer & Architect, JSR Spec Lead
>> > > Glärnischweg 10
>> > > CH - 8620 Wetzikon
>> > >
>> > > *Switzerland, Europe Zurich, GMT+1*
>> > > *Twitter: @atsticks*
>> > > *Blogs: **http://javaremarkables.blogspot.ch/
>> > > <http://javaremarkables.blogspot.ch/>*
>> > >
>> > > *Google: atsticksMobile +41-76 344 62 79*
>> > >
>> >
>>
>>
>>
>> --
>> *Anatole Tresch*
>> Java Engineer & Architect, JSR Spec Lead
>> Glärnischweg 10
>> CH - 8620 Wetzikon
>>
>> *Switzerland, Europe Zurich, GMT+1*
>> *Twitter: @atsticks*
>> *Blogs: **http://javaremarkables.blogspot.ch/
>> <http://javaremarkables.blogspot.ch/>*
>>
>> *Google: atsticksMobile +41-76 344 62 79*
>>
>
Re: Release Staging
Posted by Anatole Tresch <at...@gmail.com>.
Now the HEAD/master is back to 0.1-incubating-SNAPSHOT again.
2015-08-04 23:04 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> From my experience release-plugin is fine if all steps are successful
> otherwise you get issues like the one you speak about. jgitflow plugin is
> nicer in general - speaking from experience - but "impose" so branches
> structures which doesnt fit apache so I guess we dont have the choice yet
> but we can get in touch with maven developpers - somes are not that far
> AFAIK ;) - to enhance it.
>
> Using a 3rd party repo - ie a github repo of a *committer* - is ok since
> then the branch is pushed upstream in the workflow.
>
> 2015-08-04 22:57 GMT+02:00 Anatole Tresch <at...@gmail.com>:
>
> > Hi John
> >
> > not sure, if I got all correctly... The Deltaspike manual describes
> pushing
> > the branch to some thrid party repo, which I think is not a good
> solution,
> > it should be manageable within Apache entirely IMO. Currently the release
> > branch, after having some troubles with my tooling here, is here:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;a=tree;h=refs/heads/0.1-incubating;hb=refs/heads/0.1-incubating
> >
> > Nevertheless the master also shows already 0.2-SNAPSHOT now ;(
> > I tried to fix that but currently git server seems to be hanging... ;(
> >
> > Unfortunately I have now again to leave. IMO using the release plugin did
> > not really made things easier. It does too many things in parallel,
> where I
> > am used to have more detailed control on it. But others may have other
> > opinions.
> >
> > Best,
> > Anatole
> >
> >
> >
> >
> >
> > 2015-08-04 14:19 GMT+02:00 John D. Ament <jo...@gmail.com>:
> >
> > > Yes, go pick your children. :-)
> > >
> > > push is set to false in our release plugin config, as a result the
> > created
> > > release is not in master yet (a good thing!). We should only push it
> to
> > > master once its been voted on by both PPMC and IPMC. But we can push a
> > > release branch to do the voting on. As a result, the release is only
> on
> > > your computer.
> > >
> > > John
> > >
> > > On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch <at...@gmail.com>
> > wrote:
> > >
> > > > Yep, but as of now I have to take up my children, so it has to wait
> > for a
> > > > couple of hours, unless somebody else jumps in ;) the 0.1-incubating
> > tag
> > > > should be there on master (created by the release plugin)...
> > > >
> > > > Anatole
> > > >
> > > > 2015-08-04 14:05 GMT+02:00 John D. Ament <jo...@apache.org>:
> > > >
> > > > > Also, can you push the release branch up to the repo (not as
> master,
> > > but
> > > > > something like v0.1-incubating or equivalent) ?
> > > > > This way we have a tag and git commit to vote on.
> > > > >
> > > > > John
> > > > >
> > > > > On Tue, Aug 4, 2015 at 8:04 AM John D. Ament <
> johndament@apache.org>
> > > > > wrote:
> > > > >
> > > > > > I noticed that as well.
> > > > > >
> > > > > > I don't think that'll block the release. We can work w/ infra in
> > > > > parallel
> > > > > > to figure out the toolchain setup (probably should have done that
> > > > before
> > > > > we
> > > > > > introduced toolchain requirements, but lesson learned).
> > > > > >
> > > > > > John
> > > > > >
> > > > > > On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch <
> atsticks@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > >> What I also see is that we still have that toolchain issue with
> > the
> > > > 1.7
> > > > > >> toolchain on Jenkins... so the current build breaks on Jenkins
> ;(
> > > > > >>
> > > > > >>
> > > > > >> 2015-08-04 13:59 GMT+02:00 John D. Ament <johndament@apache.org
> >:
> > > > > >>
> > > > > >> > Agreed, it can be confusing. Looks like the only step left is
> > > > closing
> > > > > >> the
> > > > > >> > repo.
> > > > > >> >
> > > > > >> > John
> > > > > >> >
> > > > > >> > On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <
> > atsticks@gmail.com
> > > >
> > > > > >> wrote:
> > > > > >> >
> > > > > >> > > I just did what is described here:
> > > > > >> > > http://www.apache.org/dev/publishing-maven-artifacts.html
> > > > > >> > > <http://www.apache.org/dev/publishing-maven-artifacts.html>
> > > > > >> > >
> > > > > >> > > or, more especially here:
> > > > > >> > >
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > > > > >> > >
> > > > > >> > > Then:
> > > > > >> > >
> > > > >
> > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > > > > >> > >
> > > > > >> > > And finally:
> > > > > >> > >
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> > > > > >> > >
> > > > > >> > > So *section 4* here is completely misleading IMO:
> > > > > >> > > 4 - STAGE THE RELEASE FOR A VOTE¶
> > > > > >> > > <
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > > > > >> > > >
> > > > > >> > >
> > > > > >> > > mvn release:perform
> > > > > >> > >
> > > > > >> > > The release will automatically be inserted into a temporary
> > > > staging
> > > > > >> > > repository for you. See the Nexus staging documentation
> > > > > >> > > <
> > > http://www.sonatype.com/books/nexus-book/reference/staging.html>
> > > > > for
> > > > > >> > full
> > > > > >> > > details.
> > > > > >> > >
> > > > > >> > > Now you must close the staging repository to indicate to
> Nexus
> > > > that
> > > > > >> the
> > > > > >> > > build is done and to make the artifacts available. Follow
> the
> > > > steps
> > > > > >> > > inClosing
> > > > > >> > > the Staged Repository
> > > > > >> > > <
> > > > > >>
> > > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > > > >
> > > > > >> > to
> > > > > >> > > close your new repository, *this will allow your community
> to
> > > VOTE
> > > > > on
> > > > > >> the
> > > > > >> > > staged atrifacts*.
> > > > > >> > >
> > > > > >> > > But fair enough, now things look clearer again ;)
> > > > > >> > >
> > > > > >> > > Thanks
> > > > > >> > > Anatole
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <
> > > > > rmannibucau@gmail.com
> > > > > >> >:
> > > > > >> > >
> > > > > >> > > > You should stage on apache then it will get sync-ed on
> > central
> > > > no?
> > > > > >> > > > Le 4 août 2015 12:34, "Anatole Tresch" <
> atsticks@gmail.com>
> > a
> > > > > >> écrit :
> > > > > >> > > >
> > > > > >> > > > > Hi John/all
> > > > > >> > > > >
> > > > > >> > > > > I was successful in uploading the release to sonatype
> for
> > > > > staging.
> > > > > >> > > > > Unfortunately I (UID: anatole) was not able to access
> > > Nexus. I
> > > > > >> > > commented
> > > > > >> > > > on
> > > > > >> > > > > the INFRA ticket on this.
> > > > > >> > > > > Can you check, if you have access to
> > > https://oss.sonatype.org
> > > > ?
> > > > > >> > > > >
> > > > > >> > > > > Or I am doing something wrong here? The process of
> staging
> > > > > >> basically
> > > > > >> > is
> > > > > >> > > > > nothing new, since I did similar things with the money
> JSR
> > > > > >> already,
> > > > > >> > so
> > > > > >> > > > once
> > > > > >> > > > > I would be able to login we could continue with the
> > > > > release/voting
> > > > > >> > > > > process...
> > > > > >> > > > >
> > > > > >> > > > > Anatole
> > > > > >> > > > >
> > > > > >> > > > >
> > > > > >> > > > >
> > > > > >> > > > > --
> > > > > >> > > > > *Anatole Tresch*
> > > > > >> > > > > Java Engineer & Architect, JSR Spec Lead
> > > > > >> > > > > Glärnischweg 10
> > > > > >> > > > > CH - 8620 Wetzikon
> > > > > >> > > > >
> > > > > >> > > > > *Switzerland, Europe Zurich, GMT+1*
> > > > > >> > > > > *Twitter: @atsticks*
> > > > > >> > > > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > > > >> > > > > <http://javaremarkables.blogspot.ch/>*
> > > > > >> > > > >
> > > > > >> > > > > *Google: atsticksMobile +41-76 344 62 79*
> > > > > >> > > > >
> > > > > >> > > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > --
> > > > > >> > > *Anatole Tresch*
> > > > > >> > > Java Engineer & Architect, JSR Spec Lead
> > > > > >> > > Glärnischweg 10
> > > > > >> > > CH - 8620 Wetzikon
> > > > > >> > >
> > > > > >> > > *Switzerland, Europe Zurich, GMT+1*
> > > > > >> > > *Twitter: @atsticks*
> > > > > >> > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > > > >> > > <http://javaremarkables.blogspot.ch/>*
> > > > > >> > >
> > > > > >> > > *Google: atsticksMobile +41-76 344 62 79*
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> *Anatole Tresch*
> > > > > >> Java Engineer & Architect, JSR Spec Lead
> > > > > >> Glärnischweg 10
> > > > > >> CH - 8620 Wetzikon
> > > > > >>
> > > > > >> *Switzerland, Europe Zurich, GMT+1*
> > > > > >> *Twitter: @atsticks*
> > > > > >> *Blogs: **http://javaremarkables.blogspot.ch/
> > > > > >> <http://javaremarkables.blogspot.ch/>*
> > > > > >>
> > > > > >> *Google: atsticksMobile +41-76 344 62 79*
> > > > > >>
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > *Anatole Tresch*
> > > > Java Engineer & Architect, JSR Spec Lead
> > > > Glärnischweg 10
> > > > CH - 8620 Wetzikon
> > > >
> > > > *Switzerland, Europe Zurich, GMT+1*
> > > > *Twitter: @atsticks*
> > > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > > <http://javaremarkables.blogspot.ch/>*
> > > >
> > > > *Google: atsticksMobile +41-76 344 62 79*
> > > >
> > >
> >
> >
> >
> > --
> > *Anatole Tresch*
> > Java Engineer & Architect, JSR Spec Lead
> > Glärnischweg 10
> > CH - 8620 Wetzikon
> >
> > *Switzerland, Europe Zurich, GMT+1*
> > *Twitter: @atsticks*
> > *Blogs: **http://javaremarkables.blogspot.ch/
> > <http://javaremarkables.blogspot.ch/>*
> >
> > *Google: atsticksMobile +41-76 344 62 79 <%2B41-76%20344%2062%2079>*
> >
>
--
*Anatole Tresch*
Java Engineer & Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
<http://javaremarkables.blogspot.ch/>*
*Google: atsticksMobile +41-76 344 62 79 <%2B41-76%20344%2062%2079>*
Re: Release Staging
Posted by Romain Manni-Bucau <rm...@gmail.com>.
>From my experience release-plugin is fine if all steps are successful
otherwise you get issues like the one you speak about. jgitflow plugin is
nicer in general - speaking from experience - but "impose" so branches
structures which doesnt fit apache so I guess we dont have the choice yet
but we can get in touch with maven developpers - somes are not that far
AFAIK ;) - to enhance it.
Using a 3rd party repo - ie a github repo of a *committer* - is ok since
then the branch is pushed upstream in the workflow.
2015-08-04 22:57 GMT+02:00 Anatole Tresch <at...@gmail.com>:
> Hi John
>
> not sure, if I got all correctly... The Deltaspike manual describes pushing
> the branch to some thrid party repo, which I think is not a good solution,
> it should be manageable within Apache entirely IMO. Currently the release
> branch, after having some troubles with my tooling here, is here:
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;a=tree;h=refs/heads/0.1-incubating;hb=refs/heads/0.1-incubating
>
> Nevertheless the master also shows already 0.2-SNAPSHOT now ;(
> I tried to fix that but currently git server seems to be hanging... ;(
>
> Unfortunately I have now again to leave. IMO using the release plugin did
> not really made things easier. It does too many things in parallel, where I
> am used to have more detailed control on it. But others may have other
> opinions.
>
> Best,
> Anatole
>
>
>
>
>
> 2015-08-04 14:19 GMT+02:00 John D. Ament <jo...@gmail.com>:
>
> > Yes, go pick your children. :-)
> >
> > push is set to false in our release plugin config, as a result the
> created
> > release is not in master yet (a good thing!). We should only push it to
> > master once its been voted on by both PPMC and IPMC. But we can push a
> > release branch to do the voting on. As a result, the release is only on
> > your computer.
> >
> > John
> >
> > On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch <at...@gmail.com>
> wrote:
> >
> > > Yep, but as of now I have to take up my children, so it has to wait
> for a
> > > couple of hours, unless somebody else jumps in ;) the 0.1-incubating
> tag
> > > should be there on master (created by the release plugin)...
> > >
> > > Anatole
> > >
> > > 2015-08-04 14:05 GMT+02:00 John D. Ament <jo...@apache.org>:
> > >
> > > > Also, can you push the release branch up to the repo (not as master,
> > but
> > > > something like v0.1-incubating or equivalent) ?
> > > > This way we have a tag and git commit to vote on.
> > > >
> > > > John
> > > >
> > > > On Tue, Aug 4, 2015 at 8:04 AM John D. Ament <jo...@apache.org>
> > > > wrote:
> > > >
> > > > > I noticed that as well.
> > > > >
> > > > > I don't think that'll block the release. We can work w/ infra in
> > > > parallel
> > > > > to figure out the toolchain setup (probably should have done that
> > > before
> > > > we
> > > > > introduced toolchain requirements, but lesson learned).
> > > > >
> > > > > John
> > > > >
> > > > > On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch <at...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> What I also see is that we still have that toolchain issue with
> the
> > > 1.7
> > > > >> toolchain on Jenkins... so the current build breaks on Jenkins ;(
> > > > >>
> > > > >>
> > > > >> 2015-08-04 13:59 GMT+02:00 John D. Ament <jo...@apache.org>:
> > > > >>
> > > > >> > Agreed, it can be confusing. Looks like the only step left is
> > > closing
> > > > >> the
> > > > >> > repo.
> > > > >> >
> > > > >> > John
> > > > >> >
> > > > >> > On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <
> atsticks@gmail.com
> > >
> > > > >> wrote:
> > > > >> >
> > > > >> > > I just did what is described here:
> > > > >> > > http://www.apache.org/dev/publishing-maven-artifacts.html
> > > > >> > > <http://www.apache.org/dev/publishing-maven-artifacts.html>
> > > > >> > >
> > > > >> > > or, more especially here:
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > > > >> > >
> > > > >> > > Then:
> > > > >> > >
> > > >
> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > > > >> > >
> > > > >> > > And finally:
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> > > > >> > >
> > > > >> > > So *section 4* here is completely misleading IMO:
> > > > >> > > 4 - STAGE THE RELEASE FOR A VOTE¶
> > > > >> > > <
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > > > >> > > >
> > > > >> > >
> > > > >> > > mvn release:perform
> > > > >> > >
> > > > >> > > The release will automatically be inserted into a temporary
> > > staging
> > > > >> > > repository for you. See the Nexus staging documentation
> > > > >> > > <
> > http://www.sonatype.com/books/nexus-book/reference/staging.html>
> > > > for
> > > > >> > full
> > > > >> > > details.
> > > > >> > >
> > > > >> > > Now you must close the staging repository to indicate to Nexus
> > > that
> > > > >> the
> > > > >> > > build is done and to make the artifacts available. Follow the
> > > steps
> > > > >> > > inClosing
> > > > >> > > the Staged Repository
> > > > >> > > <
> > > > >>
> > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > > >
> > > > >> > to
> > > > >> > > close your new repository, *this will allow your community to
> > VOTE
> > > > on
> > > > >> the
> > > > >> > > staged atrifacts*.
> > > > >> > >
> > > > >> > > But fair enough, now things look clearer again ;)
> > > > >> > >
> > > > >> > > Thanks
> > > > >> > > Anatole
> > > > >> > >
> > > > >> > >
> > > > >> > > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <
> > > > rmannibucau@gmail.com
> > > > >> >:
> > > > >> > >
> > > > >> > > > You should stage on apache then it will get sync-ed on
> central
> > > no?
> > > > >> > > > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com>
> a
> > > > >> écrit :
> > > > >> > > >
> > > > >> > > > > Hi John/all
> > > > >> > > > >
> > > > >> > > > > I was successful in uploading the release to sonatype for
> > > > staging.
> > > > >> > > > > Unfortunately I (UID: anatole) was not able to access
> > Nexus. I
> > > > >> > > commented
> > > > >> > > > on
> > > > >> > > > > the INFRA ticket on this.
> > > > >> > > > > Can you check, if you have access to
> > https://oss.sonatype.org
> > > ?
> > > > >> > > > >
> > > > >> > > > > Or I am doing something wrong here? The process of staging
> > > > >> basically
> > > > >> > is
> > > > >> > > > > nothing new, since I did similar things with the money JSR
> > > > >> already,
> > > > >> > so
> > > > >> > > > once
> > > > >> > > > > I would be able to login we could continue with the
> > > > release/voting
> > > > >> > > > > process...
> > > > >> > > > >
> > > > >> > > > > Anatole
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > --
> > > > >> > > > > *Anatole Tresch*
> > > > >> > > > > Java Engineer & Architect, JSR Spec Lead
> > > > >> > > > > Glärnischweg 10
> > > > >> > > > > CH - 8620 Wetzikon
> > > > >> > > > >
> > > > >> > > > > *Switzerland, Europe Zurich, GMT+1*
> > > > >> > > > > *Twitter: @atsticks*
> > > > >> > > > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > > >> > > > > <http://javaremarkables.blogspot.ch/>*
> > > > >> > > > >
> > > > >> > > > > *Google: atsticksMobile +41-76 344 62 79*
> > > > >> > > > >
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > --
> > > > >> > > *Anatole Tresch*
> > > > >> > > Java Engineer & Architect, JSR Spec Lead
> > > > >> > > Glärnischweg 10
> > > > >> > > CH - 8620 Wetzikon
> > > > >> > >
> > > > >> > > *Switzerland, Europe Zurich, GMT+1*
> > > > >> > > *Twitter: @atsticks*
> > > > >> > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > > >> > > <http://javaremarkables.blogspot.ch/>*
> > > > >> > >
> > > > >> > > *Google: atsticksMobile +41-76 344 62 79*
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> *Anatole Tresch*
> > > > >> Java Engineer & Architect, JSR Spec Lead
> > > > >> Glärnischweg 10
> > > > >> CH - 8620 Wetzikon
> > > > >>
> > > > >> *Switzerland, Europe Zurich, GMT+1*
> > > > >> *Twitter: @atsticks*
> > > > >> *Blogs: **http://javaremarkables.blogspot.ch/
> > > > >> <http://javaremarkables.blogspot.ch/>*
> > > > >>
> > > > >> *Google: atsticksMobile +41-76 344 62 79*
> > > > >>
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > *Anatole Tresch*
> > > Java Engineer & Architect, JSR Spec Lead
> > > Glärnischweg 10
> > > CH - 8620 Wetzikon
> > >
> > > *Switzerland, Europe Zurich, GMT+1*
> > > *Twitter: @atsticks*
> > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > <http://javaremarkables.blogspot.ch/>*
> > >
> > > *Google: atsticksMobile +41-76 344 62 79*
> > >
> >
>
>
>
> --
> *Anatole Tresch*
> Java Engineer & Architect, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
>
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter: @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/
> <http://javaremarkables.blogspot.ch/>*
>
> *Google: atsticksMobile +41-76 344 62 79 <%2B41-76%20344%2062%2079>*
>
Re: Release Staging
Posted by Anatole Tresch <at...@gmail.com>.
Hi John
not sure, if I got all correctly... The Deltaspike manual describes pushing
the branch to some thrid party repo, which I think is not a good solution,
it should be manageable within Apache entirely IMO. Currently the release
branch, after having some troubles with my tooling here, is here:
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;a=tree;h=refs/heads/0.1-incubating;hb=refs/heads/0.1-incubating
Nevertheless the master also shows already 0.2-SNAPSHOT now ;(
I tried to fix that but currently git server seems to be hanging... ;(
Unfortunately I have now again to leave. IMO using the release plugin did
not really made things easier. It does too many things in parallel, where I
am used to have more detailed control on it. But others may have other
opinions.
Best,
Anatole
2015-08-04 14:19 GMT+02:00 John D. Ament <jo...@gmail.com>:
> Yes, go pick your children. :-)
>
> push is set to false in our release plugin config, as a result the created
> release is not in master yet (a good thing!). We should only push it to
> master once its been voted on by both PPMC and IPMC. But we can push a
> release branch to do the voting on. As a result, the release is only on
> your computer.
>
> John
>
> On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch <at...@gmail.com> wrote:
>
> > Yep, but as of now I have to take up my children, so it has to wait for a
> > couple of hours, unless somebody else jumps in ;) the 0.1-incubating tag
> > should be there on master (created by the release plugin)...
> >
> > Anatole
> >
> > 2015-08-04 14:05 GMT+02:00 John D. Ament <jo...@apache.org>:
> >
> > > Also, can you push the release branch up to the repo (not as master,
> but
> > > something like v0.1-incubating or equivalent) ?
> > > This way we have a tag and git commit to vote on.
> > >
> > > John
> > >
> > > On Tue, Aug 4, 2015 at 8:04 AM John D. Ament <jo...@apache.org>
> > > wrote:
> > >
> > > > I noticed that as well.
> > > >
> > > > I don't think that'll block the release. We can work w/ infra in
> > > parallel
> > > > to figure out the toolchain setup (probably should have done that
> > before
> > > we
> > > > introduced toolchain requirements, but lesson learned).
> > > >
> > > > John
> > > >
> > > > On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch <at...@gmail.com>
> > > wrote:
> > > >
> > > >> What I also see is that we still have that toolchain issue with the
> > 1.7
> > > >> toolchain on Jenkins... so the current build breaks on Jenkins ;(
> > > >>
> > > >>
> > > >> 2015-08-04 13:59 GMT+02:00 John D. Ament <jo...@apache.org>:
> > > >>
> > > >> > Agreed, it can be confusing. Looks like the only step left is
> > closing
> > > >> the
> > > >> > repo.
> > > >> >
> > > >> > John
> > > >> >
> > > >> > On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <atsticks@gmail.com
> >
> > > >> wrote:
> > > >> >
> > > >> > > I just did what is described here:
> > > >> > > http://www.apache.org/dev/publishing-maven-artifacts.html
> > > >> > > <http://www.apache.org/dev/publishing-maven-artifacts.html>
> > > >> > >
> > > >> > > or, more especially here:
> > > >> > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > > >> > >
> > > >> > > Then:
> > > >> > >
> > > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > > >> > >
> > > >> > > And finally:
> > > >> > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> > > >> > >
> > > >> > > So *section 4* here is completely misleading IMO:
> > > >> > > 4 - STAGE THE RELEASE FOR A VOTE¶
> > > >> > > <
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > > >> > > >
> > > >> > >
> > > >> > > mvn release:perform
> > > >> > >
> > > >> > > The release will automatically be inserted into a temporary
> > staging
> > > >> > > repository for you. See the Nexus staging documentation
> > > >> > > <
> http://www.sonatype.com/books/nexus-book/reference/staging.html>
> > > for
> > > >> > full
> > > >> > > details.
> > > >> > >
> > > >> > > Now you must close the staging repository to indicate to Nexus
> > that
> > > >> the
> > > >> > > build is done and to make the artifacts available. Follow the
> > steps
> > > >> > > inClosing
> > > >> > > the Staged Repository
> > > >> > > <
> > > >>
> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > >
> > > >> > to
> > > >> > > close your new repository, *this will allow your community to
> VOTE
> > > on
> > > >> the
> > > >> > > staged atrifacts*.
> > > >> > >
> > > >> > > But fair enough, now things look clearer again ;)
> > > >> > >
> > > >> > > Thanks
> > > >> > > Anatole
> > > >> > >
> > > >> > >
> > > >> > > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <
> > > rmannibucau@gmail.com
> > > >> >:
> > > >> > >
> > > >> > > > You should stage on apache then it will get sync-ed on central
> > no?
> > > >> > > > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a
> > > >> écrit :
> > > >> > > >
> > > >> > > > > Hi John/all
> > > >> > > > >
> > > >> > > > > I was successful in uploading the release to sonatype for
> > > staging.
> > > >> > > > > Unfortunately I (UID: anatole) was not able to access
> Nexus. I
> > > >> > > commented
> > > >> > > > on
> > > >> > > > > the INFRA ticket on this.
> > > >> > > > > Can you check, if you have access to
> https://oss.sonatype.org
> > ?
> > > >> > > > >
> > > >> > > > > Or I am doing something wrong here? The process of staging
> > > >> basically
> > > >> > is
> > > >> > > > > nothing new, since I did similar things with the money JSR
> > > >> already,
> > > >> > so
> > > >> > > > once
> > > >> > > > > I would be able to login we could continue with the
> > > release/voting
> > > >> > > > > process...
> > > >> > > > >
> > > >> > > > > Anatole
> > > >> > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > --
> > > >> > > > > *Anatole Tresch*
> > > >> > > > > Java Engineer & Architect, JSR Spec Lead
> > > >> > > > > Glärnischweg 10
> > > >> > > > > CH - 8620 Wetzikon
> > > >> > > > >
> > > >> > > > > *Switzerland, Europe Zurich, GMT+1*
> > > >> > > > > *Twitter: @atsticks*
> > > >> > > > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > >> > > > > <http://javaremarkables.blogspot.ch/>*
> > > >> > > > >
> > > >> > > > > *Google: atsticksMobile +41-76 344 62 79*
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > *Anatole Tresch*
> > > >> > > Java Engineer & Architect, JSR Spec Lead
> > > >> > > Glärnischweg 10
> > > >> > > CH - 8620 Wetzikon
> > > >> > >
> > > >> > > *Switzerland, Europe Zurich, GMT+1*
> > > >> > > *Twitter: @atsticks*
> > > >> > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > >> > > <http://javaremarkables.blogspot.ch/>*
> > > >> > >
> > > >> > > *Google: atsticksMobile +41-76 344 62 79*
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> *Anatole Tresch*
> > > >> Java Engineer & Architect, JSR Spec Lead
> > > >> Glärnischweg 10
> > > >> CH - 8620 Wetzikon
> > > >>
> > > >> *Switzerland, Europe Zurich, GMT+1*
> > > >> *Twitter: @atsticks*
> > > >> *Blogs: **http://javaremarkables.blogspot.ch/
> > > >> <http://javaremarkables.blogspot.ch/>*
> > > >>
> > > >> *Google: atsticksMobile +41-76 344 62 79*
> > > >>
> > > >
> > >
> >
> >
> >
> > --
> > *Anatole Tresch*
> > Java Engineer & Architect, JSR Spec Lead
> > Glärnischweg 10
> > CH - 8620 Wetzikon
> >
> > *Switzerland, Europe Zurich, GMT+1*
> > *Twitter: @atsticks*
> > *Blogs: **http://javaremarkables.blogspot.ch/
> > <http://javaremarkables.blogspot.ch/>*
> >
> > *Google: atsticksMobile +41-76 344 62 79*
> >
>
--
*Anatole Tresch*
Java Engineer & Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
<http://javaremarkables.blogspot.ch/>*
*Google: atsticksMobile +41-76 344 62 79 <%2B41-76%20344%2062%2079>*
Re: Release Staging
Posted by "John D. Ament" <jo...@gmail.com>.
Yes, go pick your children. :-)
push is set to false in our release plugin config, as a result the created
release is not in master yet (a good thing!). We should only push it to
master once its been voted on by both PPMC and IPMC. But we can push a
release branch to do the voting on. As a result, the release is only on
your computer.
John
On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch <at...@gmail.com> wrote:
> Yep, but as of now I have to take up my children, so it has to wait for a
> couple of hours, unless somebody else jumps in ;) the 0.1-incubating tag
> should be there on master (created by the release plugin)...
>
> Anatole
>
> 2015-08-04 14:05 GMT+02:00 John D. Ament <jo...@apache.org>:
>
> > Also, can you push the release branch up to the repo (not as master, but
> > something like v0.1-incubating or equivalent) ?
> > This way we have a tag and git commit to vote on.
> >
> > John
> >
> > On Tue, Aug 4, 2015 at 8:04 AM John D. Ament <jo...@apache.org>
> > wrote:
> >
> > > I noticed that as well.
> > >
> > > I don't think that'll block the release. We can work w/ infra in
> > parallel
> > > to figure out the toolchain setup (probably should have done that
> before
> > we
> > > introduced toolchain requirements, but lesson learned).
> > >
> > > John
> > >
> > > On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch <at...@gmail.com>
> > wrote:
> > >
> > >> What I also see is that we still have that toolchain issue with the
> 1.7
> > >> toolchain on Jenkins... so the current build breaks on Jenkins ;(
> > >>
> > >>
> > >> 2015-08-04 13:59 GMT+02:00 John D. Ament <jo...@apache.org>:
> > >>
> > >> > Agreed, it can be confusing. Looks like the only step left is
> closing
> > >> the
> > >> > repo.
> > >> >
> > >> > John
> > >> >
> > >> > On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <at...@gmail.com>
> > >> wrote:
> > >> >
> > >> > > I just did what is described here:
> > >> > > http://www.apache.org/dev/publishing-maven-artifacts.html
> > >> > > <http://www.apache.org/dev/publishing-maven-artifacts.html>
> > >> > >
> > >> > > or, more especially here:
> > >> > >
> > >> > >
> > >> >
> > >>
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > >> > >
> > >> > > Then:
> > >> > >
> > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > >> > >
> > >> > > And finally:
> > >> > >
> > >> > >
> > >> >
> > >>
> >
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> > >> > >
> > >> > > So *section 4* here is completely misleading IMO:
> > >> > > 4 - STAGE THE RELEASE FOR A VOTE¶
> > >> > > <
> > >> > >
> > >> >
> > >>
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > >> > > >
> > >> > >
> > >> > > mvn release:perform
> > >> > >
> > >> > > The release will automatically be inserted into a temporary
> staging
> > >> > > repository for you. See the Nexus staging documentation
> > >> > > <http://www.sonatype.com/books/nexus-book/reference/staging.html>
> > for
> > >> > full
> > >> > > details.
> > >> > >
> > >> > > Now you must close the staging repository to indicate to Nexus
> that
> > >> the
> > >> > > build is done and to make the artifacts available. Follow the
> steps
> > >> > > inClosing
> > >> > > the Staged Repository
> > >> > > <
> > >> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> >
> > >> > to
> > >> > > close your new repository, *this will allow your community to VOTE
> > on
> > >> the
> > >> > > staged atrifacts*.
> > >> > >
> > >> > > But fair enough, now things look clearer again ;)
> > >> > >
> > >> > > Thanks
> > >> > > Anatole
> > >> > >
> > >> > >
> > >> > > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > >> >:
> > >> > >
> > >> > > > You should stage on apache then it will get sync-ed on central
> no?
> > >> > > > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a
> > >> écrit :
> > >> > > >
> > >> > > > > Hi John/all
> > >> > > > >
> > >> > > > > I was successful in uploading the release to sonatype for
> > staging.
> > >> > > > > Unfortunately I (UID: anatole) was not able to access Nexus. I
> > >> > > commented
> > >> > > > on
> > >> > > > > the INFRA ticket on this.
> > >> > > > > Can you check, if you have access to https://oss.sonatype.org
> ?
> > >> > > > >
> > >> > > > > Or I am doing something wrong here? The process of staging
> > >> basically
> > >> > is
> > >> > > > > nothing new, since I did similar things with the money JSR
> > >> already,
> > >> > so
> > >> > > > once
> > >> > > > > I would be able to login we could continue with the
> > release/voting
> > >> > > > > process...
> > >> > > > >
> > >> > > > > Anatole
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > --
> > >> > > > > *Anatole Tresch*
> > >> > > > > Java Engineer & Architect, JSR Spec Lead
> > >> > > > > Glärnischweg 10
> > >> > > > > CH - 8620 Wetzikon
> > >> > > > >
> > >> > > > > *Switzerland, Europe Zurich, GMT+1*
> > >> > > > > *Twitter: @atsticks*
> > >> > > > > *Blogs: **http://javaremarkables.blogspot.ch/
> > >> > > > > <http://javaremarkables.blogspot.ch/>*
> > >> > > > >
> > >> > > > > *Google: atsticksMobile +41-76 344 62 79*
> > >> > > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > *Anatole Tresch*
> > >> > > Java Engineer & Architect, JSR Spec Lead
> > >> > > Glärnischweg 10
> > >> > > CH - 8620 Wetzikon
> > >> > >
> > >> > > *Switzerland, Europe Zurich, GMT+1*
> > >> > > *Twitter: @atsticks*
> > >> > > *Blogs: **http://javaremarkables.blogspot.ch/
> > >> > > <http://javaremarkables.blogspot.ch/>*
> > >> > >
> > >> > > *Google: atsticksMobile +41-76 344 62 79*
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> *Anatole Tresch*
> > >> Java Engineer & Architect, JSR Spec Lead
> > >> Glärnischweg 10
> > >> CH - 8620 Wetzikon
> > >>
> > >> *Switzerland, Europe Zurich, GMT+1*
> > >> *Twitter: @atsticks*
> > >> *Blogs: **http://javaremarkables.blogspot.ch/
> > >> <http://javaremarkables.blogspot.ch/>*
> > >>
> > >> *Google: atsticksMobile +41-76 344 62 79*
> > >>
> > >
> >
>
>
>
> --
> *Anatole Tresch*
> Java Engineer & Architect, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
>
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter: @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/
> <http://javaremarkables.blogspot.ch/>*
>
> *Google: atsticksMobile +41-76 344 62 79*
>
Re: Release Staging
Posted by Anatole Tresch <at...@gmail.com>.
Yep, but as of now I have to take up my children, so it has to wait for a
couple of hours, unless somebody else jumps in ;) the 0.1-incubating tag
should be there on master (created by the release plugin)...
Anatole
2015-08-04 14:05 GMT+02:00 John D. Ament <jo...@apache.org>:
> Also, can you push the release branch up to the repo (not as master, but
> something like v0.1-incubating or equivalent) ?
> This way we have a tag and git commit to vote on.
>
> John
>
> On Tue, Aug 4, 2015 at 8:04 AM John D. Ament <jo...@apache.org>
> wrote:
>
> > I noticed that as well.
> >
> > I don't think that'll block the release. We can work w/ infra in
> parallel
> > to figure out the toolchain setup (probably should have done that before
> we
> > introduced toolchain requirements, but lesson learned).
> >
> > John
> >
> > On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch <at...@gmail.com>
> wrote:
> >
> >> What I also see is that we still have that toolchain issue with the 1.7
> >> toolchain on Jenkins... so the current build breaks on Jenkins ;(
> >>
> >>
> >> 2015-08-04 13:59 GMT+02:00 John D. Ament <jo...@apache.org>:
> >>
> >> > Agreed, it can be confusing. Looks like the only step left is closing
> >> the
> >> > repo.
> >> >
> >> > John
> >> >
> >> > On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <at...@gmail.com>
> >> wrote:
> >> >
> >> > > I just did what is described here:
> >> > > http://www.apache.org/dev/publishing-maven-artifacts.html
> >> > > <http://www.apache.org/dev/publishing-maven-artifacts.html>
> >> > >
> >> > > or, more especially here:
> >> > >
> >> > >
> >> >
> >>
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> >> > >
> >> > > Then:
> >> > >
> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> >> > >
> >> > > And finally:
> >> > >
> >> > >
> >> >
> >>
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> >> > >
> >> > > So *section 4* here is completely misleading IMO:
> >> > > 4 - STAGE THE RELEASE FOR A VOTE¶
> >> > > <
> >> > >
> >> >
> >>
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> >> > > >
> >> > >
> >> > > mvn release:perform
> >> > >
> >> > > The release will automatically be inserted into a temporary staging
> >> > > repository for you. See the Nexus staging documentation
> >> > > <http://www.sonatype.com/books/nexus-book/reference/staging.html>
> for
> >> > full
> >> > > details.
> >> > >
> >> > > Now you must close the staging repository to indicate to Nexus that
> >> the
> >> > > build is done and to make the artifacts available. Follow the steps
> >> > > inClosing
> >> > > the Staged Repository
> >> > > <
> >> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage>
> >> > to
> >> > > close your new repository, *this will allow your community to VOTE
> on
> >> the
> >> > > staged atrifacts*.
> >> > >
> >> > > But fair enough, now things look clearer again ;)
> >> > >
> >> > > Thanks
> >> > > Anatole
> >> > >
> >> > >
> >> > > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <
> rmannibucau@gmail.com
> >> >:
> >> > >
> >> > > > You should stage on apache then it will get sync-ed on central no?
> >> > > > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a
> >> écrit :
> >> > > >
> >> > > > > Hi John/all
> >> > > > >
> >> > > > > I was successful in uploading the release to sonatype for
> staging.
> >> > > > > Unfortunately I (UID: anatole) was not able to access Nexus. I
> >> > > commented
> >> > > > on
> >> > > > > the INFRA ticket on this.
> >> > > > > Can you check, if you have access to https://oss.sonatype.org ?
> >> > > > >
> >> > > > > Or I am doing something wrong here? The process of staging
> >> basically
> >> > is
> >> > > > > nothing new, since I did similar things with the money JSR
> >> already,
> >> > so
> >> > > > once
> >> > > > > I would be able to login we could continue with the
> release/voting
> >> > > > > process...
> >> > > > >
> >> > > > > Anatole
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > *Anatole Tresch*
> >> > > > > Java Engineer & Architect, JSR Spec Lead
> >> > > > > Glärnischweg 10
> >> > > > > CH - 8620 Wetzikon
> >> > > > >
> >> > > > > *Switzerland, Europe Zurich, GMT+1*
> >> > > > > *Twitter: @atsticks*
> >> > > > > *Blogs: **http://javaremarkables.blogspot.ch/
> >> > > > > <http://javaremarkables.blogspot.ch/>*
> >> > > > >
> >> > > > > *Google: atsticksMobile +41-76 344 62 79*
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > *Anatole Tresch*
> >> > > Java Engineer & Architect, JSR Spec Lead
> >> > > Glärnischweg 10
> >> > > CH - 8620 Wetzikon
> >> > >
> >> > > *Switzerland, Europe Zurich, GMT+1*
> >> > > *Twitter: @atsticks*
> >> > > *Blogs: **http://javaremarkables.blogspot.ch/
> >> > > <http://javaremarkables.blogspot.ch/>*
> >> > >
> >> > > *Google: atsticksMobile +41-76 344 62 79*
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> *Anatole Tresch*
> >> Java Engineer & Architect, JSR Spec Lead
> >> Glärnischweg 10
> >> CH - 8620 Wetzikon
> >>
> >> *Switzerland, Europe Zurich, GMT+1*
> >> *Twitter: @atsticks*
> >> *Blogs: **http://javaremarkables.blogspot.ch/
> >> <http://javaremarkables.blogspot.ch/>*
> >>
> >> *Google: atsticksMobile +41-76 344 62 79*
> >>
> >
>
--
*Anatole Tresch*
Java Engineer & Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
<http://javaremarkables.blogspot.ch/>*
*Google: atsticksMobile +41-76 344 62 79*
Re: Release Staging
Posted by "John D. Ament" <jo...@apache.org>.
Also, can you push the release branch up to the repo (not as master, but
something like v0.1-incubating or equivalent) ?
This way we have a tag and git commit to vote on.
John
On Tue, Aug 4, 2015 at 8:04 AM John D. Ament <jo...@apache.org> wrote:
> I noticed that as well.
>
> I don't think that'll block the release. We can work w/ infra in parallel
> to figure out the toolchain setup (probably should have done that before we
> introduced toolchain requirements, but lesson learned).
>
> John
>
> On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch <at...@gmail.com> wrote:
>
>> What I also see is that we still have that toolchain issue with the 1.7
>> toolchain on Jenkins... so the current build breaks on Jenkins ;(
>>
>>
>> 2015-08-04 13:59 GMT+02:00 John D. Ament <jo...@apache.org>:
>>
>> > Agreed, it can be confusing. Looks like the only step left is closing
>> the
>> > repo.
>> >
>> > John
>> >
>> > On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <at...@gmail.com>
>> wrote:
>> >
>> > > I just did what is described here:
>> > > http://www.apache.org/dev/publishing-maven-artifacts.html
>> > > <http://www.apache.org/dev/publishing-maven-artifacts.html>
>> > >
>> > > or, more especially here:
>> > >
>> > >
>> >
>> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
>> > >
>> > > Then:
>> > > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
>> > >
>> > > And finally:
>> > >
>> > >
>> >
>> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
>> > >
>> > > So *section 4* here is completely misleading IMO:
>> > > 4 - STAGE THE RELEASE FOR A VOTE¶
>> > > <
>> > >
>> >
>> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
>> > > >
>> > >
>> > > mvn release:perform
>> > >
>> > > The release will automatically be inserted into a temporary staging
>> > > repository for you. See the Nexus staging documentation
>> > > <http://www.sonatype.com/books/nexus-book/reference/staging.html> for
>> > full
>> > > details.
>> > >
>> > > Now you must close the staging repository to indicate to Nexus that
>> the
>> > > build is done and to make the artifacts available. Follow the steps
>> > > inClosing
>> > > the Staged Repository
>> > > <
>> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage>
>> > to
>> > > close your new repository, *this will allow your community to VOTE on
>> the
>> > > staged atrifacts*.
>> > >
>> > > But fair enough, now things look clearer again ;)
>> > >
>> > > Thanks
>> > > Anatole
>> > >
>> > >
>> > > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <rmannibucau@gmail.com
>> >:
>> > >
>> > > > You should stage on apache then it will get sync-ed on central no?
>> > > > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a
>> écrit :
>> > > >
>> > > > > Hi John/all
>> > > > >
>> > > > > I was successful in uploading the release to sonatype for staging.
>> > > > > Unfortunately I (UID: anatole) was not able to access Nexus. I
>> > > commented
>> > > > on
>> > > > > the INFRA ticket on this.
>> > > > > Can you check, if you have access to https://oss.sonatype.org ?
>> > > > >
>> > > > > Or I am doing something wrong here? The process of staging
>> basically
>> > is
>> > > > > nothing new, since I did similar things with the money JSR
>> already,
>> > so
>> > > > once
>> > > > > I would be able to login we could continue with the release/voting
>> > > > > process...
>> > > > >
>> > > > > Anatole
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > *Anatole Tresch*
>> > > > > Java Engineer & Architect, JSR Spec Lead
>> > > > > Glärnischweg 10
>> > > > > CH - 8620 Wetzikon
>> > > > >
>> > > > > *Switzerland, Europe Zurich, GMT+1*
>> > > > > *Twitter: @atsticks*
>> > > > > *Blogs: **http://javaremarkables.blogspot.ch/
>> > > > > <http://javaremarkables.blogspot.ch/>*
>> > > > >
>> > > > > *Google: atsticksMobile +41-76 344 62 79*
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > *Anatole Tresch*
>> > > Java Engineer & Architect, JSR Spec Lead
>> > > Glärnischweg 10
>> > > CH - 8620 Wetzikon
>> > >
>> > > *Switzerland, Europe Zurich, GMT+1*
>> > > *Twitter: @atsticks*
>> > > *Blogs: **http://javaremarkables.blogspot.ch/
>> > > <http://javaremarkables.blogspot.ch/>*
>> > >
>> > > *Google: atsticksMobile +41-76 344 62 79*
>> > >
>> >
>>
>>
>>
>> --
>> *Anatole Tresch*
>> Java Engineer & Architect, JSR Spec Lead
>> Glärnischweg 10
>> CH - 8620 Wetzikon
>>
>> *Switzerland, Europe Zurich, GMT+1*
>> *Twitter: @atsticks*
>> *Blogs: **http://javaremarkables.blogspot.ch/
>> <http://javaremarkables.blogspot.ch/>*
>>
>> *Google: atsticksMobile +41-76 344 62 79*
>>
>
Re: Release Staging
Posted by "John D. Ament" <jo...@apache.org>.
I noticed that as well.
I don't think that'll block the release. We can work w/ infra in parallel
to figure out the toolchain setup (probably should have done that before we
introduced toolchain requirements, but lesson learned).
John
On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch <at...@gmail.com> wrote:
> What I also see is that we still have that toolchain issue with the 1.7
> toolchain on Jenkins... so the current build breaks on Jenkins ;(
>
>
> 2015-08-04 13:59 GMT+02:00 John D. Ament <jo...@apache.org>:
>
> > Agreed, it can be confusing. Looks like the only step left is closing
> the
> > repo.
> >
> > John
> >
> > On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <at...@gmail.com>
> wrote:
> >
> > > I just did what is described here:
> > > http://www.apache.org/dev/publishing-maven-artifacts.html
> > > <http://www.apache.org/dev/publishing-maven-artifacts.html>
> > >
> > > or, more especially here:
> > >
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > >
> > > Then:
> > > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> > >
> > > And finally:
> > >
> > >
> >
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> > >
> > > So *section 4* here is completely misleading IMO:
> > > 4 - STAGE THE RELEASE FOR A VOTE¶
> > > <
> > >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > > >
> > >
> > > mvn release:perform
> > >
> > > The release will automatically be inserted into a temporary staging
> > > repository for you. See the Nexus staging documentation
> > > <http://www.sonatype.com/books/nexus-book/reference/staging.html> for
> > full
> > > details.
> > >
> > > Now you must close the staging repository to indicate to Nexus that the
> > > build is done and to make the artifacts available. Follow the steps
> > > inClosing
> > > the Staged Repository
> > > <http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> >
> > to
> > > close your new repository, *this will allow your community to VOTE on
> the
> > > staged atrifacts*.
> > >
> > > But fair enough, now things look clearer again ;)
> > >
> > > Thanks
> > > Anatole
> > >
> > >
> > > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> > >
> > > > You should stage on apache then it will get sync-ed on central no?
> > > > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a écrit
> :
> > > >
> > > > > Hi John/all
> > > > >
> > > > > I was successful in uploading the release to sonatype for staging.
> > > > > Unfortunately I (UID: anatole) was not able to access Nexus. I
> > > commented
> > > > on
> > > > > the INFRA ticket on this.
> > > > > Can you check, if you have access to https://oss.sonatype.org ?
> > > > >
> > > > > Or I am doing something wrong here? The process of staging
> basically
> > is
> > > > > nothing new, since I did similar things with the money JSR already,
> > so
> > > > once
> > > > > I would be able to login we could continue with the release/voting
> > > > > process...
> > > > >
> > > > > Anatole
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > *Anatole Tresch*
> > > > > Java Engineer & Architect, JSR Spec Lead
> > > > > Glärnischweg 10
> > > > > CH - 8620 Wetzikon
> > > > >
> > > > > *Switzerland, Europe Zurich, GMT+1*
> > > > > *Twitter: @atsticks*
> > > > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > > > <http://javaremarkables.blogspot.ch/>*
> > > > >
> > > > > *Google: atsticksMobile +41-76 344 62 79*
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > *Anatole Tresch*
> > > Java Engineer & Architect, JSR Spec Lead
> > > Glärnischweg 10
> > > CH - 8620 Wetzikon
> > >
> > > *Switzerland, Europe Zurich, GMT+1*
> > > *Twitter: @atsticks*
> > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > <http://javaremarkables.blogspot.ch/>*
> > >
> > > *Google: atsticksMobile +41-76 344 62 79*
> > >
> >
>
>
>
> --
> *Anatole Tresch*
> Java Engineer & Architect, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
>
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter: @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/
> <http://javaremarkables.blogspot.ch/>*
>
> *Google: atsticksMobile +41-76 344 62 79*
>
Re: Release Staging
Posted by Anatole Tresch <at...@gmail.com>.
What I also see is that we still have that toolchain issue with the 1.7
toolchain on Jenkins... so the current build breaks on Jenkins ;(
2015-08-04 13:59 GMT+02:00 John D. Ament <jo...@apache.org>:
> Agreed, it can be confusing. Looks like the only step left is closing the
> repo.
>
> John
>
> On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <at...@gmail.com> wrote:
>
> > I just did what is described here:
> > http://www.apache.org/dev/publishing-maven-artifacts.html
> > <http://www.apache.org/dev/publishing-maven-artifacts.html>
> >
> > or, more especially here:
> >
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> >
> > Then:
> > http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
> >
> > And finally:
> >
> >
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
> >
> > So *section 4* here is completely misleading IMO:
> > 4 - STAGE THE RELEASE FOR A VOTE¶
> > <
> >
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> > >
> >
> > mvn release:perform
> >
> > The release will automatically be inserted into a temporary staging
> > repository for you. See the Nexus staging documentation
> > <http://www.sonatype.com/books/nexus-book/reference/staging.html> for
> full
> > details.
> >
> > Now you must close the staging repository to indicate to Nexus that the
> > build is done and to make the artifacts available. Follow the steps
> > inClosing
> > the Staged Repository
> > <http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage>
> to
> > close your new repository, *this will allow your community to VOTE on the
> > staged atrifacts*.
> >
> > But fair enough, now things look clearer again ;)
> >
> > Thanks
> > Anatole
> >
> >
> > 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> >
> > > You should stage on apache then it will get sync-ed on central no?
> > > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a écrit :
> > >
> > > > Hi John/all
> > > >
> > > > I was successful in uploading the release to sonatype for staging.
> > > > Unfortunately I (UID: anatole) was not able to access Nexus. I
> > commented
> > > on
> > > > the INFRA ticket on this.
> > > > Can you check, if you have access to https://oss.sonatype.org ?
> > > >
> > > > Or I am doing something wrong here? The process of staging basically
> is
> > > > nothing new, since I did similar things with the money JSR already,
> so
> > > once
> > > > I would be able to login we could continue with the release/voting
> > > > process...
> > > >
> > > > Anatole
> > > >
> > > >
> > > >
> > > > --
> > > > *Anatole Tresch*
> > > > Java Engineer & Architect, JSR Spec Lead
> > > > Glärnischweg 10
> > > > CH - 8620 Wetzikon
> > > >
> > > > *Switzerland, Europe Zurich, GMT+1*
> > > > *Twitter: @atsticks*
> > > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > > <http://javaremarkables.blogspot.ch/>*
> > > >
> > > > *Google: atsticksMobile +41-76 344 62 79*
> > > >
> > >
> >
> >
> >
> > --
> > *Anatole Tresch*
> > Java Engineer & Architect, JSR Spec Lead
> > Glärnischweg 10
> > CH - 8620 Wetzikon
> >
> > *Switzerland, Europe Zurich, GMT+1*
> > *Twitter: @atsticks*
> > *Blogs: **http://javaremarkables.blogspot.ch/
> > <http://javaremarkables.blogspot.ch/>*
> >
> > *Google: atsticksMobile +41-76 344 62 79*
> >
>
--
*Anatole Tresch*
Java Engineer & Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
<http://javaremarkables.blogspot.ch/>*
*Google: atsticksMobile +41-76 344 62 79*
Re: Release Staging
Posted by "John D. Ament" <jo...@apache.org>.
Agreed, it can be confusing. Looks like the only step left is closing the
repo.
John
On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch <at...@gmail.com> wrote:
> I just did what is described here:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> <http://www.apache.org/dev/publishing-maven-artifacts.html>
>
> or, more especially here:
>
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
>
> Then:
> http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
>
> And finally:
>
> http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
>
> So *section 4* here is completely misleading IMO:
> 4 - STAGE THE RELEASE FOR A VOTE¶
> <
> http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
> >
>
> mvn release:perform
>
> The release will automatically be inserted into a temporary staging
> repository for you. See the Nexus staging documentation
> <http://www.sonatype.com/books/nexus-book/reference/staging.html> for full
> details.
>
> Now you must close the staging repository to indicate to Nexus that the
> build is done and to make the artifacts available. Follow the steps
> inClosing
> the Staged Repository
> <http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage> to
> close your new repository, *this will allow your community to VOTE on the
> staged atrifacts*.
>
> But fair enough, now things look clearer again ;)
>
> Thanks
> Anatole
>
>
> 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
>
> > You should stage on apache then it will get sync-ed on central no?
> > Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a écrit :
> >
> > > Hi John/all
> > >
> > > I was successful in uploading the release to sonatype for staging.
> > > Unfortunately I (UID: anatole) was not able to access Nexus. I
> commented
> > on
> > > the INFRA ticket on this.
> > > Can you check, if you have access to https://oss.sonatype.org ?
> > >
> > > Or I am doing something wrong here? The process of staging basically is
> > > nothing new, since I did similar things with the money JSR already, so
> > once
> > > I would be able to login we could continue with the release/voting
> > > process...
> > >
> > > Anatole
> > >
> > >
> > >
> > > --
> > > *Anatole Tresch*
> > > Java Engineer & Architect, JSR Spec Lead
> > > Glärnischweg 10
> > > CH - 8620 Wetzikon
> > >
> > > *Switzerland, Europe Zurich, GMT+1*
> > > *Twitter: @atsticks*
> > > *Blogs: **http://javaremarkables.blogspot.ch/
> > > <http://javaremarkables.blogspot.ch/>*
> > >
> > > *Google: atsticksMobile +41-76 344 62 79*
> > >
> >
>
>
>
> --
> *Anatole Tresch*
> Java Engineer & Architect, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
>
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter: @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/
> <http://javaremarkables.blogspot.ch/>*
>
> *Google: atsticksMobile +41-76 344 62 79*
>
Re: Release Staging
Posted by Anatole Tresch <at...@gmail.com>.
I just did what is described here:
http://www.apache.org/dev/publishing-maven-artifacts.html
<http://www.apache.org/dev/publishing-maven-artifacts.html>
or, more especially here:
http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
Then: http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
And finally:
http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
So *section 4* here is completely misleading IMO:
4 - STAGE THE RELEASE FOR A VOTE¶
<http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote>
mvn release:perform
The release will automatically be inserted into a temporary staging
repository for you. See the Nexus staging documentation
<http://www.sonatype.com/books/nexus-book/reference/staging.html> for full
details.
Now you must close the staging repository to indicate to Nexus that the
build is done and to make the artifacts available. Follow the steps inClosing
the Staged Repository
<http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage> to
close your new repository, *this will allow your community to VOTE on the
staged atrifacts*.
But fair enough, now things look clearer again ;)
Thanks
Anatole
2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau <rm...@gmail.com>:
> You should stage on apache then it will get sync-ed on central no?
> Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a écrit :
>
> > Hi John/all
> >
> > I was successful in uploading the release to sonatype for staging.
> > Unfortunately I (UID: anatole) was not able to access Nexus. I commented
> on
> > the INFRA ticket on this.
> > Can you check, if you have access to https://oss.sonatype.org ?
> >
> > Or I am doing something wrong here? The process of staging basically is
> > nothing new, since I did similar things with the money JSR already, so
> once
> > I would be able to login we could continue with the release/voting
> > process...
> >
> > Anatole
> >
> >
> >
> > --
> > *Anatole Tresch*
> > Java Engineer & Architect, JSR Spec Lead
> > Glärnischweg 10
> > CH - 8620 Wetzikon
> >
> > *Switzerland, Europe Zurich, GMT+1*
> > *Twitter: @atsticks*
> > *Blogs: **http://javaremarkables.blogspot.ch/
> > <http://javaremarkables.blogspot.ch/>*
> >
> > *Google: atsticksMobile +41-76 344 62 79*
> >
>
--
*Anatole Tresch*
Java Engineer & Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
<http://javaremarkables.blogspot.ch/>*
*Google: atsticksMobile +41-76 344 62 79*
Re: Release Staging
Posted by Romain Manni-Bucau <rm...@gmail.com>.
You should stage on apache then it will get sync-ed on central no?
Le 4 août 2015 12:34, "Anatole Tresch" <at...@gmail.com> a écrit :
> Hi John/all
>
> I was successful in uploading the release to sonatype for staging.
> Unfortunately I (UID: anatole) was not able to access Nexus. I commented on
> the INFRA ticket on this.
> Can you check, if you have access to https://oss.sonatype.org ?
>
> Or I am doing something wrong here? The process of staging basically is
> nothing new, since I did similar things with the money JSR already, so once
> I would be able to login we could continue with the release/voting
> process...
>
> Anatole
>
>
>
> --
> *Anatole Tresch*
> Java Engineer & Architect, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
>
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter: @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/
> <http://javaremarkables.blogspot.ch/>*
>
> *Google: atsticksMobile +41-76 344 62 79*
>