Age doesnt for sure, user number does. To be maybe clearer today main
[weaver] user is bval. Maybe we can check stats regarding downloads, nexus
can surely help.
Le 5 juin 2014 01:40, "Gary Gregory" a écrit :
> I agree with Sebb, age is irrelevant. BY still matters.
>
> Gary
>
> Original
I agree with Sebb, age is irrelevant. BY still matters.
Gary
Original message From: Emmanuel Bourg
Date:06/04/2014 18:49 (GMT-05:00)
To: Commons Developers List
Subject: Re: [VOTE] Release Apache Commons Weaver 1.1 based on RC1
Le 04/06/2014 23:58, sebb a écrit :
> Huh
+1 that's mainly an internal lib (more than public one ATM) so no issue
with API *now*
Le 4 juin 2014 23:49, "Emmanuel Bourg" a écrit :
> Le 04/06/2014 23:58, sebb a écrit :
>
> > Huh?
> > Why should it matter how old the component is?
> > Breaking the API can still cause serious problems.
>
> If
Le 04/06/2014 23:58, sebb a écrit :
> Huh?
> Why should it matter how old the component is?
> Breaking the API can still cause serious problems.
If a young component isn't yet widely used a binary incompatible change
is less likely to create a problem. It's not like [lang] or [io] which
have been
On 4 June 2014 22:12, Emmanuel Bourg wrote:
> Le 04/06/2014 23:02, Gary Gregory a écrit :
>> aalmost -1 because there is no Clirr report on the site so I cannot
>> tell if 1.1 breaks or maintains BC.
>
> Commons Weaver 1.0 has been released 3 months ago, I don't think it
> would be fair to blo
As this is a multimodule component, report content tends to be more correct
when relegated to the module level. Please see:
http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver-processor/project-reports.html
http://people.apache.org/~mbenson/commons-weaver-1.1-rc1/commons-weaver
Le 04/06/2014 23:02, Gary Gregory a écrit :
> aalmost -1 because there is no Clirr report on the site so I cannot
> tell if 1.1 breaks or maintains BC.
Commons Weaver 1.0 has been released 3 months ago, I don't think it
would be fair to block the release for a breaking change with such a
young
I kinda expect FindBugs, PMD and Checkstyle reports...
Gary
On Wed, Jun 4, 2014 at 5:02 PM, Gary Gregory wrote:
> aalmost -1 because there is no Clirr report on the site so I cannot
> tell if 1.1 breaks or maintains BC.
>
> Gary
>
>
> On Wed, Jun 4, 2014 at 3:44 PM, Matt Benson wrote:
>
>
aalmost -1 because there is no Clirr report on the site so I cannot
tell if 1.1 breaks or maintains BC.
Gary
On Wed, Jun 4, 2014 at 3:44 PM, Matt Benson wrote:
> I would like to release the [weaver] component.
>
> Apache Commons Weaver 1.1 RC1 is available for review at:
> https://dist.a
I would like to release the [weaver] component.
Apache Commons Weaver 1.1 RC1 is available for review at:
https://dist.apache.org/repos/dist/dev/commons/weaver/ (r5487, md5s and
sha1s in 5488).
Maven artifacts are at:
https://repository.apache.org/content/repositories/orgapachecommons-1033/
Le 04/06/2014 17:41, Gary Gregory a écrit :
> Hi All,
>
> It's that time again.
>
> Please provide feedback for our Apache Commons Board Report, June 4 2014,
> provided below.
It looks find to me, thanks Gary.
Luc
>
> Thank you,
> Gary
> -
>
> Apache Commons Board Report, June 4 2014
>
> Th
Hi All,
It's that time again.
Please provide feedback for our Apache Commons Board Report, June 4 2014,
provided below.
Thank you,
Gary
-
Apache Commons Board Report, June 4 2014
The Apache Commons project focuses on all aspects of reusable Java
components.
The Apache Commons components are w
12 matches
Mail list logo
