On 9/13/06, Upayavira <[EMAIL PROTECTED]> wrote:
So how does Felix proceed now? Accept that the rules have just changed
on it, after spending some months under the view that a release _wasn't_
necessary to graduation, and go back and do something it would have done
months ago had it not been told
On Thu, Sep 14, 2006 at 04:00:37AM +0100, Upayavira wrote:
> Justin Erenkrantz wrote:
> > On 9/13/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> >> personally speaking, i would not support the gradudation any project
> >> that has not demonstrated that they understand the apache releases
>
Justin Erenkrantz wrote:
On 9/13/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
personally speaking, i would not support the gradudation any project
that has not demonstrated that they understand the apache releases
policy. doing this is much easier and quicker than creating a proper
relea
In accordance with the incubator release procedure (see below) the
Apache ActiveMQ community has voted on and approved the 4.1 release of
the ActiveMQ maven plugins. These plugins are required for the maven
build of the ActiveMQ. These artifacts are only targeted for the
ActiveMQ project to cons
The ServiceMix community voted on and approved to release
the 3.0-incubating version [1]. Pursuant to the Releases section of
the Incubation Policy and we would now like to request the
permission of the Incubator PMC to publish this release.
The release / download page is available at [2]:
[1]
h
On 9/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
In accordance with the incubator release procedure (see below) the
Apache ActiveMQ community has voted on and approved the 4.1 release of
the ActiveMQ maven plugins. These plugins are required for the maven
build of the ActiveMQ. These artifa
On Thursday September 14 2006 12:18 pm, Hiram Chirino wrote:
> In accordance with the incubator release procedure (see below) the
> Apache ActiveMQ community has voted on and approved the 4.1 release of
> the ActiveMQ maven plugins. These plugins are required for the maven
> build of the ActiveMQ
> FWIW, I don't see mime4j listed on the IP clearance page.
Neither do I, although the CLAs and Software Grant have long been on file
(since about two years ago). I don't know yet if it got overlooked, since
it was shortly after we created the IP Clearance form; or misplaced, but
I'll fix.
Do people want to have a BOF at ApacheCon to discuss general Incubator
business?
See http://wiki.apache.org/apachecon/BirdsOfaFeatherUs06
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
On 9/14/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
On 9/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
>
> You can checkout the binary build here:
> http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/
+1
Thanks!
a few notes:
the MANIFEST files are probabl
On 9/14/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
The ServiceMix community voted on and approved to release
the 3.0-incubating version [1]. Pursuant to the Releases section of
the Incubation Policy and we would now like to request the
permission of the Incubator PMC to publish this release.
There was a long going thread about the M2 repo for the incubating
projects snapshots. Was there any conclusion to that? Can we publish
them somewhere now?
We need to expose Cayenne snapshots for integration testing... I
guess if we still can't publish them on Apache servers, we'll have to
On 9/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
On 9/14/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> On 9/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> a few notes:
>
> the MANIFEST files are probably not compliant with the Sun standards.
> would be better with Extension-N
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be useful for podlings (mentors and release managers
in particular)?
if so, would it be appropriate to check the source in som
On 9/14/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be useful for podlings (mentors and release managers
in particul
Just curious: what kind of issues does it track down?
Eelco
On 9/14/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be
Just out of interest, what would this tool specifically check for? In
what does it differ from checkstyle, pmd and findbugs?
Will it work with Java/C/C++/Python sources?
Best regards,
Martijn
On 9/14/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
i have a basic tool that i've been runni
On Thursday September 14 2006 5:31 pm, robert burrell donkin wrote:
> i have a basic tool that i've been running against the source releases
> recently. it's simple but helps to track down some basic issues. no
> documentation.
>
> would this tool be useful for podlings (mentors and release manager
On 9/14/06, robert burrell donkin <[EMAIL PROTECTED]> wrote:
On 9/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> This is not a distribution but just a
> set of jars that our main distribution will depend on.
-1
every distributed artifact must be signed. jars are distributions.
they must b
robert burrell donkin wrote:
> http://svn.apache.org/repos/asf/incubator/servicemix/trunk/samples/servicemix-web/src/webapp/mktree.js
>
> worries me. its license does not appear to be suitable for
> redistribution.
It seems so. I'll see what I can do about that.
>
> OASIS and W3C licensed docume
20 matches
Mail list logo
