Re: [VOTE] Release Configuration 2.1 based on RC1

+1 Based on the src zip, the ASC, MD5, and SHA1 are OK. RAT and Clirr checks OK. Tests pass, site builds, reports look good. Files in tag matches src zip except for PROPOSAL.html. Tested with: Apache Maven 3.4.0-SNAPSHOT (90f26c279af9738735be8f84f60dcf21b6244e24; 2016-07-22T08:23:04-07:00) Ma

Maven, Clirr and BCEL

FYI: It looks like some one took the initiative and PR'd updating the Maven Clirr plugin to BCEL 6.0: https://github.com/mojohaus/clirr-maven-plugin/pull/18 Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: [ALL] Create a pom parent 41 release

Now that BCEL 6.0 is out, can the parent POM make Clirr use BCEL 6? Gary On Mon, Jul 25, 2016 at 8:03 PM, Charles Honton wrote: > Any objections to creating a release for pom parent 41? > This currently has one change; two new profiles that enable clirr or > japicmp for binary compatibility rep

Re: [ALL] Create a pom parent 41 release

Go for it. Gary On Mon, Jul 25, 2016 at 8:03 PM, Charles Honton wrote: > Any objections to creating a release for pom parent 41? > This currently has one change; two new profiles that enable clirr or > japicmp for binary compatibility reports. > > chas >

[VOTE] Release CRYPTO 1.0.0 based on RC1

Hi all, Apache Commons CRYPTO was established at May 9, 2016, There are presently numbers of resolved issues fix in CRYPTO. We also fix the legal issue. Apache Commons CRYPTO 1.0.0 is available for review here: https://dist.apache.org/repos/dist/dev/commons/crypto (rev 14538) The tag is

[ALL] Create a pom parent 41 release

Any objections to creating a release for pom parent 41? This currently has one change; two new profiles that enable clirr or japicmp for binary compatibility reports. chas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.

Re: [All] regarding the granting and revoking of commit privileges

I didn't see any mention, but if you're a committer on any other Apache project, you're automatically added as a committer here. Not sure about joining the PMC, though, but I'm sure it's the same as all the other Apache projects (vote by PMC in the private mailing list). On 25 July 2016 at 10:06,

Re: [All] regarding the granting and revoking of commit privileges

Thanks guys. Much appreciation, -Rob > On Jul 25, 2016, at 10:45 AM, Gary Gregory wrote: > > See also http://www.apache.org/dev/pmc.html > > Folks usually resign PMC membership and/or project commit rights when they > want to quit a project. I've not seen a procedure to "fire" a person. > > Ga

Re: [All] regarding the granting and revoking of commit privileges

See also http://www.apache.org/dev/pmc.html Folks usually resign PMC membership and/or project commit rights when they want to quit a project. I've not seen a procedure to "fire" a person. Gary On Jul 25, 2016 7:40 AM, "Mark Thomas" wrote: > On 25/07/2016 15:34, Rob Tompkins wrote: > > All, >

Re: [All] regarding the granting and revoking of commit privileges

On 2016-07-25, Rob Tompkins wrote: > So the question at hand stems from a project at my day job. We, much > like with commons, have the committing members of the project vote on > new folks becoming committers. But we are curious about how to go > about ending someone's commit privileges. How does

Re: [All] regarding the granting and revoking of commit privileges

On 25/07/2016 15:34, Rob Tompkins wrote: > All, > > As a relatively new member to the community, I have yet see a vote on > a committer come to pass, so you'll have to pardon my naivety on this > matter. > > So the question at hand stems from a project at my day job. We, much > like with commons,

[All] regarding the granting and revoking of commit privileges

All, As a relatively new member to the community, I have yet see a vote on a committer come to pass, so you'll have to pardon my naivety on this matter. So the question at hand stems from a project at my day job. We, much like with commons, have the committing members of the project vote on ne