Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=80077&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 23:28:41 -0700
Finished at: Wed 23 Apr 2008 23:28:49 -0700
Total time: 7s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=80077&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 23:28:41 -0700
Finished at: Wed 23 Apr 2008 23:28:49 -0700
Total time: 7s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=80068&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 22:19:34 -0700
Finished at: Wed 23 Apr 2008 22:19:44 -0700
Total time: 9s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=80068&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 22:19:34 -0700
Finished at: Wed 23 Apr 2008 22:19:44 -0700
Total time: 9s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=80008&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 20:22:18 -0700
Finished at: Wed 23 Apr 2008 20:22:28 -0700
Total time: 9s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=80008&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 20:22:18 -0700
Finished at: Wed 23 Apr 2008 20:22:28 -0700
Total time: 9s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79948&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 16:50:24 -0700
Finished at: Wed 23 Apr 2008 16:50:37 -0700
Total time: 12s
Build Trigger: Schedule
Build Numb
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79948&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 16:50:24 -0700
Finished at: Wed 23 Apr 2008 16:50:37 -0700
Total time: 12s
Build Trigger: Schedule
Build Numb
On 4/23/08, Matt Benson <[EMAIL PROTECTED]> wrote:
> What is the status of the instructions at
> http://wiki.apache.org/commons/CreatingReleases ? I
> tried:
>
> mvn -Prc release:prepare
>
> This seemed to work okay, made the tag, etc.
>
> mvn -Prc release:perform
>
> This seemed to go okay,
On 4/23/08, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> > The amount of security rigor applied that would cause an unsigned key
> > to be a blocking factor for signing releases would probably also
> > discount the above from being acceptable.
> >
>
> Why is that? I cannot follow that argument
>
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79912&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 12:04:00 -0700
Finished at: Wed 23 Apr 2008 12:04:11 -0700
Total time: 10s
Build Trigger: Schedule
Build Numb
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79912&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 12:04:00 -0700
Finished at: Wed 23 Apr 2008 12:04:11 -0700
Total time: 10s
Build Trigger: Schedule
Build Numb
--- Torsten Curdt <[EMAIL PROTECTED]> wrote:
> > How would that work logistically? I publish RC
> > artifacts, and once they're voted on, you sign the
> > same artifacts that presumably you personally
> > reviewed? Doesn't that necessarily force us -not-
> to
> > use the full mvn process?
>
>
The signing key has to be in the KEYS file; the KEYS file is normally
in SVN which implies that the person who updated it has an ASF login.
Indeed ...forgot about that path. I'll shut up then :)
cheers
--
Torsten
-
To unsubscr
On Wed, 2008-04-23 at 09:30 +0100, sebb wrote:
> 2008/4/23 Torsten Curdt <[EMAIL PROTECTED]>:
> >
> > > Risks are mitigated to an arguably acceptable level by wrappering the
> > > entire release process at Apache around the point to point secure
> > > transport guarantee that signing is meant to p
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79887&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 08:39:29 -0700
Finished at: Wed 23 Apr 2008 08:39:46 -0700
Total time: 17s
Build Trigger: Schedule
Build Numb
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79887&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 08:39:29 -0700
Finished at: Wed 23 Apr 2008 08:39:46 -0700
Total time: 17s
Build Trigger: Schedule
Build Numb
2008/4/23 Torsten Curdt <[EMAIL PROTECTED]>:
>
> > Risks are mitigated to an arguably acceptable level by wrappering the
> > entire release process at Apache around the point to point secure
> > transport guarantee that signing is meant to provide.
> >
>
> That holds only true if you don't use mir
2008/4/21 Siegfried Goeschl <[EMAIL PROTECTED]>:
> Hi Sebastian,
>
> under http://people.apache.org/~sgoeschl/download/commons-exec/ you will an
> improved version of the test distribution - it could/should pass most of the
> test on OpenVMS ;-) ... can you give it a run?
>
Sorry for the del
How would that work logistically? I publish RC
artifacts, and once they're voted on, you sign the
same artifacts that presumably you personally
reviewed? Doesn't that necessarily force us -not- to
use the full mvn process?
Indeed - that's would mean not using the gpg maven plugin
Let's get h
--- Torsten Curdt <[EMAIL PROTECTED]> wrote:
> > Risks are mitigated to an arguably acceptable
> level by wrappering the
> > entire release process at Apache around the point
> to point secure
> > transport guarantee that signing is meant to
> provide.
>
> That holds only true if you don't use m
What is the status of the instructions at
http://wiki.apache.org/commons/CreatingReleases ? I
tried:
mvn -Prc release:prepare
This seemed to work okay, made the tag, etc.
mvn -Prc release:perform
This seemed to go okay, until it uploaded the site to
live and I had to restore the site manually.
--- Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 22, 2008 at 6:48 PM, Matt Benson
> <[EMAIL PROTECTED]> wrote:
> > Where can I go to see the specific details for the
> > failed test?
>
> http://tinyurl.com/6h75tg
>
> This test has been failing randomly - i.e. sometimes
> is passes
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-id has an issue affecting its community integration.
This issue affects 1
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79856&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 01:47:11 -0700
Finished at: Wed 23 Apr 2008 01:47:20 -0700
Total time: 8s
Build Trigger: Schedule
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=79856&projectId=178
Build statistics:
State: Error
Previous State: Error
Started at: Wed 23 Apr 2008 01:47:11 -0700
Finished at: Wed 23 Apr 2008 01:47:20 -0700
Total time: 8s
Build Trigger: Schedule
Build Numbe
Torsten Curdt schrieb:
>> Risks are mitigated to an arguably acceptable level by wrappering the
>> entire release process at Apache around the point to point secure
>> transport guarantee that signing is meant to provide.
>
> That holds only true if you don't use mirrors and people get the
> releas
Risks are mitigated to an arguably acceptable level by wrappering the
entire release process at Apache around the point to point secure
transport guarantee that signing is meant to provide.
That holds only true if you don't use mirrors and people get the
releases directly from us.
I am gene
On Apr 22, 2008, at 21:48, Daniel F. Savarese wrote:
Is there any particular reason why he can't work on the project
anyway?
Of course not ...you are mote than welcome to contribute :)
cheers
--
Torsten
-
To unsubscribe, e-
29 matches
Mail list logo
