Well, since it's not the only modification, I'll do it.
On 14/10/2016 15:02, Mike Kienenberger wrote:
Don't revert on my behalf. It doesn't matter to me if I'm listed as
a committer in the pom, and it can always be corrected in a future
release.
But did you ever publish the staging URL? I d
Remove Antonio from the PMC, as he asked to go emeritus.
I just checked if I had enough karma to do it myself (editing of
private/committers/board/committee-info.txt), and it worked.
So no worry, Nathan, nothing to do for you :-)
Claude
On 14/10/2016 15:29, Nathan Bubna wrote:
Uh, oh. Wh
Uh, oh. What do i need to do here? Sorry guys, not meaning to be slacking.
On Fri, Oct 14, 2016 at 6:14 AM, Antonio Petrelli <
antonio.petre...@gmail.com> wrote:
> 2016-10-14 14:56 GMT+02:00 Claude Brisson :
>
> > Ah, and Antonio asked to become emeritus (but the change hasn't been
> > pushed upw
2016-10-14 14:56 GMT+02:00 Claude Brisson :
> Ah, and Antonio asked to become emeritus (but the change hasn't been
> pushed upwards, I think only Nathan can do it).
>
Yep :-)
Antonio
Don't revert on my behalf. It doesn't matter to me if I'm listed as
a committer in the pom, and it can always be corrected in a future
release.
But did you ever publish the staging URL? I don't remember seeing it.
On Fri, Oct 14, 2016 at 8:56 AM, Claude Brisson wrote:
> I change my vote to -1
I change my vote to -1: I forgot Mike as new commiter... (sorry about
that, Mike!). Also, Dishara (who worked on the JSR 223 scripting) is not
listed.
Ah, and Antonio asked to become emeritus (but the change hasn't been
pushed upwards, I think only Nathan can do it).
If you don't mind, I'll
On 11/10/2016 16:02, Mike Kienenberger wrote:
I took a look at the MyFaces release page, which in turn points to the
following url. Starting at this section, it does look like you now
have all of the pieces you need in place: prepare the release,
perform the release, close the respository, tak
+1
On Tue, Oct 11, 2016 at 5:11 AM, Claude Brisson wrote:
> Hi.
>
> Before staging the release candidate for velocity-engine, I must first
> release the version 2 of velocity-master.
>
> It only contains a pom.xml with the list of PMCs and devs, and enumerate
> the mailing lists, and can be seen
I took a look at the MyFaces release page, which in turn points to the
following url. Starting at this section, it does look like you now
have all of the pieces you need in place: prepare the release,
perform the release, close the respository, take the vote.
http://www.apache.org/dev/publishing
2016-10-11 15:31 GMT+02:00 Sergiu Dumitriu :
> That's normal, that URL points to a virtual push-only directory, and you
> also need a staging ID to identify which staging repo to push to. When
> using the browser, a new random ID was generated. It seems that nexus is
> behind it, you must log in a
That's normal, that URL points to a virtual push-only directory, and you
also need a staging ID to identify which staging repo to push to. When
using the browser, a new random ID was generated. It seems that nexus is
behind it, you must log in and look at the staging repos to actually
publish the s
2016-10-11 15:23 GMT+02:00 Claude Brisson :
> Oh, but I *did* call release:perform.
>
OK I'm seeing it, it's called:
orgapachevelocity-1000
Now you have to close it, so nothing else can be deployed to it.
Antonio
+1
release:prepare only publishes the tag, unless configured not to do that
automatically. release:perform builds and publishes the artifacts.
On Oct 11, 2016 8:12 AM, "Claude Brisson" wrote:
Hi.
Before staging the release candidate for velocity-engine, I must first
release the version 2 of ve
Oh, but I *did* call release:perform. Here's the log:
> mvn release:perform
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Velocity - Master POM 3-SNAPSHOT
[INFO]
---
On 11/10/2016 14:43, Mike Kienenberger wrote:
On Tue, Oct 11, 2016 at 8:11 AM, Claude Brisson wrote:
(I don't know where snapshots and prepared releases do land on
https://repository.apache.org , I was unable to find them on
https://repository.apache.org after the release:prepare call, which
2016-10-11 14:11 GMT+02:00 Claude Brisson :
> (I don't know where snapshots and prepared releases do land on
> https://repository.apache.org , I was unable to find them on
> https://repository.apache.org after the release:prepare call, which
> apparently went smoothly, maybe there is some delay...
On Tue, Oct 11, 2016 at 8:11 AM, Claude Brisson wrote:
> (I don't know where snapshots and prepared releases do land on
> https://repository.apache.org , I was unable to find them on
> https://repository.apache.org after the release:prepare call, which
> apparently went smoothly, maybe there is so
Hi.
Before staging the release candidate for velocity-engine, I must first
release the version 2 of velocity-master.
It only contains a pom.xml with the list of PMCs and devs, and enumerate
the mailing lists, and can be seen here:
http://svn.apache.org/viewvc/velocity/maven/tags/velocity-ma
18 matches
Mail list logo
