Re: Release process updates (try 2)

On Mon, Jul 1, 2013 at 4:20 AM, sebb wrote: > Reminder: all this thread is just about is adding the following lines > to vote e-mails: > > SVN Tag: > > https://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.9.1/ > (r1496317

Re: Release process updates

2013/6/26 sebb : > The mission of the ASF is to release software as source, and to ensure > that the released source is available under the Apache Licence. Excuse me but I have always understand the ASF mission as building communities around softwares. Community over Code and not Process over Code

Re: [VOTE] Apache 3.1.0

On 1 July 2013 06:52, sebb wrote: > Another problem: the NOTICE file contains the following spurious text: > >= >== NOTICE file corresponding to the section 4 d of== >== the Apache License, Ve

Re: Maven 3.1.0-beta-1

It may be Maven or one of the plugins that changed as a result of updating the default plugins. I have a several very large builds and performance seems the same. I will set up the performance framework for the core[1], and I have a profiler for plugins that I will cleanup. I think it best to ge

Re: [VOTE] Apache 3.1.0

Jason van Zyl wrote: Staged distribution: https://repository.apache.org/content/repositories/maven-084/org/apache/maven/apache-maven/3.1.0/ +1 non-binding on the binary/execution, seems to work fine on a mixture of my projects. --

maven-surefire pull request: Parallel Computer

GitHub user Tibor17 opened a pull request: https://github.com/apache/maven-surefire/pull/25 Parallel Computer This is an implementation of PC moved from my private repo to surefire project. It will fix and improve the PC. You can merge this pull request into a Git repository by

Re: Release process updates (try 2)

On 30 June 2013 23:32, Benson Margulies wrote: > On the one hand, I think that, in many Apache communities, comparing the > source release to the VCS is the exception and not the rule, and may never > have happened, even once. (I think that there is at least an even chance > that some crusty veter

Re: Release process updates (try 2)

On 30 June 2013 19:20, sebb wrote: > The mission of the ASF is to release software as source, and to ensure > that the released source is available under the Apache Licence. > > Before a release can be approved it must be voted on by the PMC. > The review process needs to establish that the propos

Re: Release process updates (try 2)

On the one hand, I think that, in many Apache communities, comparing the source release to the VCS is the exception and not the rule, and may never have happened, even once. (I think that there is at least an even chance that some crusty veteran of httpd will arrive in this thread and call me out o

Re: Unique Git coordinates (was: Release process updates (try 2))

On 30 June 2013 23:28, Stephen Connolly wrote: > On Sunday, 30 June 2013, sebb wrote: > >> On 30 June 2013 21:56, Fred Cooke > >> wrote: >> >> >> >> OK, so what is the Git command to download a copy of the sources that >> >> >> > are part of the hash? >> >> >> > >> > git checkout >> >> Does not w

Re: svn commit: r2333 - /release/maven/enforcer/

On 30 June 2013 22:36, Robert Scholte wrote: > Enforcer is more than only the plugin, it also contains an API for other > developers to write their own plugins, plus a set of standard rules. These > are always released at once. For that reason it has its own folder. OK, understood. > IIRC recent

Re: Unique Git coordinates (was: Release process updates (try 2))

On Sunday, 30 June 2013, sebb wrote: > On 30 June 2013 21:56, Fred Cooke > > wrote: > >> > >> OK, so what is the Git command to download a copy of the sources that > >> > > are part of the hash? > >> > > > > git checkout > > Does not work for me. Until I hear otherwise, the reviewers for whom t

Re: svn commit: r2333 - /release/maven/enforcer/

Enforcer is more than only the plugin, it also contains an API for other developers to write their own plugins, plus a set of standard rules. These are always released at once. For that reason it has its own folder. IIRC recentely we've been asked to always put the distributions in source c

Re: [VOTE] Apache 3.1.0

Another problem: the NOTICE file contains the following spurious text: = == NOTICE file corresponding to the section 4 d of== == the Apache License, Version 2.0,

Unique Git coordinates (was: Release process updates (try 2))

On 30 June 2013 21:56, Fred Cooke wrote: >> >> OK, so what is the Git command to download a copy of the sources that >> > are part of the hash? >> > > git checkout Does not work for me. I get the following error message: fatal: Not a git repository (or any of the parent directories): .git Thi

Re: Release process updates (try 2)

> > OK, so what is the Git command to download a copy of the sources that > are part of the hash? > git checkout Then observe the tree. You can also export an archive, though I don't recall the exact command off the top of my hand. > Don't I need to know something about the Git repo it comes f

Re: svn commit: r2333 - /release/maven/enforcer/

On 30 June 2013 21:25, wrote: > Author: rfscholte > Date: Sun Jun 30 20:25:21 2013 > New Revision: 2333 > > Log: > Store all required release files of every available enforcer version > Added: > release/maven/enforcer/ Surely enforcer should be under release/maven/plugins? Or maybe I have

Re: Release process updates (try 2)

On 30 June 2013 19:48, Fred Cooke wrote: > For Git the only thing that is needed is the unique 40 character hash such > as this: > > FreeAir:youtube-dl fred$ git rev-parse HEAD > 48bfb5f2387ab47e1973d9db0782a9af66ffc4e6 OK, so what is the Git command to download a copy of the sources that are par

Re: [VOTE] Release Maven Enforcer version 1.3 (take 2)

On 30 June 2013 21:04, Stephen Connolly wrote: > On Sunday, 30 June 2013, sebb wrote: > >> On 29 June 2013 11:47, Robert Scholte > >> wrote: >> > Hi Sebb, >> > >> > none of these files will end up in Maven Central, they are all used for >> > tests. >> >> However, they do end up in the source relea

Re: Poposed Sandbox plugins - digest and gpg:signfiles

You mean releases that don't go to the standard release repo? Yes it's technically possible but it becomes a dangerous thin line between official release and one that bypasses the usual asf process. --mobile On Jun 22, 2013, at 8:07 PM, sebb wrote: > On 23 June 2013 01:00, Olivier Lamy wrote:

Re: [ANN] Apache Maven Enforcer Plugin 1.3 Released

I've used the announcement template[1] If this isn't complete, please file a Jira issue. Robert [1] http://maven.apache.org/developers/release/maven-project-release-procedure.html Op Sun, 30 Jun 2013 22:00:54 +0200 schreef sebb : On 30 June 2013 20:55, Robert Scholte wrote: The Apache Ma

Re: [VOTE] Release Maven Enforcer version 1.3 (take 2)

On Sunday, 30 June 2013, sebb wrote: > On 29 June 2013 11:47, Robert Scholte > > wrote: > > Hi Sebb, > > > > none of these files will end up in Maven Central, they are all used for > > tests. > > However, they do end up in the source release which is published via > the ASF mirrors. > It's vital t

Re: [ANN] Apache Maven Enforcer Plugin 1.3 Released

On 30 June 2013 20:55, Robert Scholte wrote: > The Apache Maven team is pleased to announce the release of the Maven > Enforcer Plugin, version 1.3 > > The Enforcer plugin provides goals to control certain environmental > constraints such as Maven version, JDK version and OS family along with many

[ANN] Apache Maven Enforcer Plugin 1.3 Released

The Apache Maven team is pleased to announce the release of the Maven Enforcer Plugin, version 1.3 The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user created rules. h

Re: [VOTE] Apache 3.1.0

On 30 June 2013 20:00, Jason van Zyl wrote: > Here are the release bits for 3.1.0: > > Release notes: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 > > Staging repository: > https://repository.apache.org/content/repositories/maven-084/ > > Staged distribution: >

Re: [VOTE] Apache 3.1.0

So probably this is: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=893ca28a1da9d5f51ac03827af98bb730128f9f2 :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sun, Jun 30, 2013 at 9:00 PM, Jaso

Re: [VOTE] Apache 3.1.0

+1 (non-binding) tested with some projects. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sun, Jun 30, 2013 at 9:00 PM, Jason van Zyl wrote: > Here are the release bits for 3.1.0: > > Release notes: > https:/

Re: Release process updates (try 2)

Fine with me. Thanks for the explanation sebb. Gary On Jun 30, 2013, at 14:20, sebb wrote: > The mission of the ASF is to release software as source, and to ensure > that the released source is available under the Apache Licence. > > Before a release can be approved it must be voted on by the P

Re: Maven 3.1.0-beta-1

Hi I see this as well in our corporate aggregator POM that builds everything. This 124 module build succeeds with Maven 3.0.5, but fails with java.lang.OutOfMemoryError: PermGen space after 108 modules when using Maven 3.1.0-alpha-1. Sorry but I can't share the project. Are there any free tools t

[VOTE] Apache 3.1.0

Here are the release bits for 3.1.0: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-084/ Staged distribution: https://repository.apache.org/content/repositories/maven-084/

Re: Release process updates (try 2)

For Git the only thing that is needed is the unique 40 character hash such as this: FreeAir:youtube-dl fred$ git rev-parse HEAD 48bfb5f2387ab47e1973d9db0782a9af66ffc4e6 It's just sloppy not to do this; if a quality release process is required, so is the SVN rev number. If "good enough" is OK, the

Release process updates (try 2)

The mission of the ASF is to release software as source, and to ensure that the released source is available under the Apache Licence. Before a release can be approved it must be voted on by the PMC. The review process needs to establish that the proposed source release meets those aims. It's all

Re: [VOTE] Release Maven Enforcer version 1.3 (take 2)

On 29 June 2013 11:47, Robert Scholte wrote: > Hi Sebb, > > none of these files will end up in Maven Central, they are all used for > tests. However, they do end up in the source release which is published via the ASF mirrors. It's vital that all released source files have the appropriate header.

Re: Donay

2013/6/29 Robert Scholte : > Hi, > > recently I noticed a new thing at the Jira of Codehaus: Donay > It is saying "Facing this issue? Let the Developers help you out." > > Here Donay explains how it works: > https://secure.donay.com/site/how-it-works > > Has this been shared with the community? AFA