You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Antonio Petrelli <an...@gmail.com> on 2010/06/09 09:56:50 UTC
[VOTE] Move future Velocity releases to Apache's Nexus Pro instance
All,
I am proposing that we change our release process so that we can
leverage the Apache instance of Sonatype Nexus Professional. I will
personally perform the necessary steps to get the appropriate
information documented and the appropriate access granted. I estimate
the steps to be as follows -
- Request access to the Nexus repository. I will make sure to gather
all of the required details (nexus login, etc.) so that the necessary
information can be documented on the following page:
http://wiki.apache.org/velocity/ReleaseProcess
- Make any changes to pom.xml files so that the various plugins will
know about nexus acting as the snapshot and staging repository,
after all the Maven reorganization is finished.
- Update the documentation referenced above
Once you have had a chance to review the documentation and necessary
steps, please respond with a vote:
[ ] +1 Agree
[ ] +0 Indifferent, but do not disagree
[ ] -0 Disagree, but not sure why
[ ] -1 Do not agree, leave release procedure as-is
Everyone who has a vested interest is invited to vote. Votes by PMC
members are considered binding. A vote passes if there are at least
three binding +1s and more +1s than -1s.
The vote will remain open for at least 72 hours, longer upon request.
Thanks
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Antonio Petrelli <an...@gmail.com>.
2010/6/15 Antonio Petrelli <an...@gmail.com>:
> I will create the INFRA issue ASAP.
Here it is:
https://issues.apache.org/jira/browse/INFRA-2798
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Antonio Petrelli <an...@gmail.com>.
Here are the results:
+1 binding: Nathan, Claude, Will
+1 non binding: Antonio
I will create the INFRA issue ASAP.
Thanks
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Will Glass-Husain <wg...@gmail.com>.
+1
On Wed, Jun 9, 2010 at 8:16 AM, Claude Brisson <cl...@renegat.net> wrote:
> +1, as long as there is a sustained effort in documenting everything
>
> Claude
>
> On mer., 2010-06-09 at 07:53 -0700, Nathan Bubna wrote:
> > Ok, +1
> >
> > On Wed, Jun 9, 2010 at 7:44 AM, Antonio Petrelli
> > <an...@gmail.com> wrote:
> > > 2010/6/9 Nathan Bubna <nb...@gmail.com>:
> > >> Not all of us are familiar with this. Could you explain the benefits?
> > >
> > > The benefit is that staging Maven artifacts is no more a problem,
> > > since Nexus (professional edition) allows an easy promotion to the
> > > main repository.
> > > The main Apache pom contains most of the configuration needed to
> > > deploy artifacts correctly.
> > > And this is the standard at Apache now.
> > >
> > >> And would this entail abandoning our Ant release process for Maven?
> > >
> > > No, the binaries will be uploaded in people.apache.org, only Maven
> > > artifacts are interested. Moreover, Nexus has a nice "Staging upload"
> > > feature, that allows to upload Maven artifacts in a staging
> > > repository, to allow the vote process.
> > >
> > > Antonio
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> > > For additional commands, e-mail: dev-help@velocity.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> > For additional commands, e-mail: dev-help@velocity.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Claude Brisson <cl...@renegat.net>.
+1, as long as there is a sustained effort in documenting everything
Claude
On mer., 2010-06-09 at 07:53 -0700, Nathan Bubna wrote:
> Ok, +1
>
> On Wed, Jun 9, 2010 at 7:44 AM, Antonio Petrelli
> <an...@gmail.com> wrote:
> > 2010/6/9 Nathan Bubna <nb...@gmail.com>:
> >> Not all of us are familiar with this. Could you explain the benefits?
> >
> > The benefit is that staging Maven artifacts is no more a problem,
> > since Nexus (professional edition) allows an easy promotion to the
> > main repository.
> > The main Apache pom contains most of the configuration needed to
> > deploy artifacts correctly.
> > And this is the standard at Apache now.
> >
> >> And would this entail abandoning our Ant release process for Maven?
> >
> > No, the binaries will be uploaded in people.apache.org, only Maven
> > artifacts are interested. Moreover, Nexus has a nice "Staging upload"
> > feature, that allows to upload Maven artifacts in a staging
> > repository, to allow the vote process.
> >
> > Antonio
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> > For additional commands, e-mail: dev-help@velocity.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Nathan Bubna <nb...@gmail.com>.
Ok, +1
On Wed, Jun 9, 2010 at 7:44 AM, Antonio Petrelli
<an...@gmail.com> wrote:
> 2010/6/9 Nathan Bubna <nb...@gmail.com>:
>> Not all of us are familiar with this. Could you explain the benefits?
>
> The benefit is that staging Maven artifacts is no more a problem,
> since Nexus (professional edition) allows an easy promotion to the
> main repository.
> The main Apache pom contains most of the configuration needed to
> deploy artifacts correctly.
> And this is the standard at Apache now.
>
>> And would this entail abandoning our Ant release process for Maven?
>
> No, the binaries will be uploaded in people.apache.org, only Maven
> artifacts are interested. Moreover, Nexus has a nice "Staging upload"
> feature, that allows to upload Maven artifacts in a staging
> repository, to allow the vote process.
>
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Antonio Petrelli <an...@gmail.com>.
2010/6/9 Nathan Bubna <nb...@gmail.com>:
> Not all of us are familiar with this. Could you explain the benefits?
The benefit is that staging Maven artifacts is no more a problem,
since Nexus (professional edition) allows an easy promotion to the
main repository.
The main Apache pom contains most of the configuration needed to
deploy artifacts correctly.
And this is the standard at Apache now.
> And would this entail abandoning our Ant release process for Maven?
No, the binaries will be uploaded in people.apache.org, only Maven
artifacts are interested. Moreover, Nexus has a nice "Staging upload"
feature, that allows to upload Maven artifacts in a staging
repository, to allow the vote process.
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Nathan Bubna <nb...@gmail.com>.
On Wed, Jun 9, 2010 at 12:56 AM, Antonio Petrelli
<an...@gmail.com> wrote:
> All,
>
> I am proposing that we change our release process so that we can
> leverage the Apache instance of Sonatype Nexus Professional.
Not all of us are familiar with this. Could you explain the benefits?
And would this entail abandoning our Ant release process for Maven?
The latter would be very hard to vote for without seeing how your
sandbox maven reorg turns out.
> I will
> personally perform the necessary steps to get the appropriate
> information documented and the appropriate access granted. I estimate
> the steps to be as follows -
>
> - Request access to the Nexus repository. I will make sure to gather
> all of the required details (nexus login, etc.) so that the necessary
> information can be documented on the following page:
> http://wiki.apache.org/velocity/ReleaseProcess
>
> - Make any changes to pom.xml files so that the various plugins will
> know about nexus acting as the snapshot and staging repository,
> after all the Maven reorganization is finished.
>
> - Update the documentation referenced above
>
> Once you have had a chance to review the documentation and necessary
> steps, please respond with a vote:
>
> [ ] +1 Agree
> [ ] +0 Indifferent, but do not disagree
> [ ] -0 Disagree, but not sure why
> [ ] -1 Do not agree, leave release procedure as-is
>
> Everyone who has a vested interest is invited to vote. Votes by PMC
> members are considered binding. A vote passes if there are at least
> three binding +1s and more +1s than -1s.
>
> The vote will remain open for at least 72 hours, longer upon request.
>
> Thanks
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: [VOTE] Move future Velocity releases to Apache's Nexus Pro
instance
Posted by Antonio Petrelli <an...@gmail.com>.
2010/6/9 Antonio Petrelli <an...@gmail.com>:
> [X] +1 Agree
+1 (non binding)
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org