You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by Steve Blackmon <sb...@apache.org> on 2020/03/12 13:45:31 UTC
Working on streams-project-0.6.1-rc1
Hello team,
Just a note that I am working on generating a release candidate.
It’s been a while since I did this last, and on first pass our script did not create a staging repository.
I’ll keep working on this and hopefully figure out what’s going wrong soon.
If I can’t figure it out by tomorrow, I will capture the full series of commands and logs for everyone to inspect.
Anyway watch this space for a VOTE in the next week or so.
—
These are the key commands:
mvn -Papache-release release:prepare -DpushChanges=false -DautoVersionSubmodules=true -DreleaseVersion=0.6.1 -DdevelopmentVersion=0.6.2-SNAPSHOT -Dtag=streams-project-0.6.1-rc1
mvn -Papache-release clean install release:perform -Darguments='-Dmaven.test.skip.exec=true' -Dgoals=deploy -DlocalRepoDirectory=. -DlocalCheckout=true
Instead of deploying release artifacts to a new staging repo, we just get a newly deployed SNAPSHOT
Re: Working on streams-project-0.6.1-rc1
Posted by Trevor Grant <tr...@gmail.com>.
I'm available to do some testing, I've got a house reno project going on so
can't do much bug bashing- but happy to help w other stuff.
On Fri, Mar 13, 2020 at 4:14 AM Suneel Marthi <sm...@apache.org> wrote:
> I can work with u on this over the weekend Steve and help get a release
> candidate out.
>
> On Fri, Mar 13, 2020 at 1:21 AM Steve Blackmon <sb...@apache.org>
> wrote:
>
> > Today I’ve observed the release plugin, run from release.sh script,
> upload
> > multiple release artifacts from multiple modules.
> >
> > Unfortunately someway through the process failed due to
> > repository.apache.org timeouts.
> >
> > Will try again tomorrow.
> > On Mar 12, 2020, 8:45 AM -0500, Steve Blackmon <sb...@apache.org>,
> > wrote:
> > > Hello team,
> > >
> > > Just a note that I am working on generating a release candidate.
> > >
> > > It’s been a while since I did this last, and on first pass our script
> > did not create a staging repository.
> > >
> > > I’ll keep working on this and hopefully figure out what’s going wrong
> > soon.
> > >
> > > If I can’t figure it out by tomorrow, I will capture the full series of
> > commands and logs for everyone to inspect.
> > >
> > > Anyway watch this space for a VOTE in the next week or so.
> > >
> > > —
> > >
> > > These are the key commands:
> > >
> > > mvn -Papache-release release:prepare -DpushChanges=false
> > -DautoVersionSubmodules=true -DreleaseVersion=0.6.1
> > -DdevelopmentVersion=0.6.2-SNAPSHOT -Dtag=streams-project-0.6.1-rc1
> > > mvn -Papache-release clean install release:perform
> > -Darguments='-Dmaven.test.skip.exec=true' -Dgoals=deploy
> > -DlocalRepoDirectory=. -DlocalCheckout=true
> > >
> > > Instead of deploying release artifacts to a new staging repo, we just
> > get a newly deployed SNAPSHOT
> > >
> >
>
Re: Working on streams-project-0.6.1-rc1
Posted by Suneel Marthi <sm...@apache.org>.
I can work with u on this over the weekend Steve and help get a release
candidate out.
On Fri, Mar 13, 2020 at 1:21 AM Steve Blackmon <sb...@apache.org> wrote:
> Today I’ve observed the release plugin, run from release.sh script, upload
> multiple release artifacts from multiple modules.
>
> Unfortunately someway through the process failed due to
> repository.apache.org timeouts.
>
> Will try again tomorrow.
> On Mar 12, 2020, 8:45 AM -0500, Steve Blackmon <sb...@apache.org>,
> wrote:
> > Hello team,
> >
> > Just a note that I am working on generating a release candidate.
> >
> > It’s been a while since I did this last, and on first pass our script
> did not create a staging repository.
> >
> > I’ll keep working on this and hopefully figure out what’s going wrong
> soon.
> >
> > If I can’t figure it out by tomorrow, I will capture the full series of
> commands and logs for everyone to inspect.
> >
> > Anyway watch this space for a VOTE in the next week or so.
> >
> > —
> >
> > These are the key commands:
> >
> > mvn -Papache-release release:prepare -DpushChanges=false
> -DautoVersionSubmodules=true -DreleaseVersion=0.6.1
> -DdevelopmentVersion=0.6.2-SNAPSHOT -Dtag=streams-project-0.6.1-rc1
> > mvn -Papache-release clean install release:perform
> -Darguments='-Dmaven.test.skip.exec=true' -Dgoals=deploy
> -DlocalRepoDirectory=. -DlocalCheckout=true
> >
> > Instead of deploying release artifacts to a new staging repo, we just
> get a newly deployed SNAPSHOT
> >
>
Re: Working on streams-project-0.6.1-rc1
Posted by Steve Blackmon <sb...@apache.org>.
Today I’ve observed the release plugin, run from release.sh script, upload multiple release artifacts from multiple modules.
Unfortunately someway through the process failed due to repository.apache.org timeouts.
Will try again tomorrow.
On Mar 12, 2020, 8:45 AM -0500, Steve Blackmon <sb...@apache.org>, wrote:
> Hello team,
>
> Just a note that I am working on generating a release candidate.
>
> It’s been a while since I did this last, and on first pass our script did not create a staging repository.
>
> I’ll keep working on this and hopefully figure out what’s going wrong soon.
>
> If I can’t figure it out by tomorrow, I will capture the full series of commands and logs for everyone to inspect.
>
> Anyway watch this space for a VOTE in the next week or so.
>
> —
>
> These are the key commands:
>
> mvn -Papache-release release:prepare -DpushChanges=false -DautoVersionSubmodules=true -DreleaseVersion=0.6.1 -DdevelopmentVersion=0.6.2-SNAPSHOT -Dtag=streams-project-0.6.1-rc1
> mvn -Papache-release clean install release:perform -Darguments='-Dmaven.test.skip.exec=true' -Dgoals=deploy -DlocalRepoDirectory=. -DlocalCheckout=true
>
> Instead of deploying release artifacts to a new staging repo, we just get a newly deployed SNAPSHOT
>