Re: slow SVN when committing 4,200 files

Am Donnerstag, 15. Oktober 2015 schrieb Michael Osipov : > Am 2015-10-15 um 02:26 schrieb Tibor Digana: > >> Hi, >> >> It takes 4 to 5 hour to complete the commit of surefire site on SVN. >> The site is about 4,200 files and 820 folders. >> >> I am doing it on people.apache.org machine; otherwise

Re: slow SVN when committing 4,200 files

Am 2015-10-15 um 02:26 schrieb Tibor Digana: Hi, It takes 4 to 5 hour to complete the commit of surefire site on SVN. The site is about 4,200 files and 820 folders. I am doing it on people.apache.org machine; otherwise Maven scm-publish would fail on my localhost. Are you certain that homes o

[VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

Hi, We solved 57 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12331679 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC Staging repo: https://

slow SVN when committing 4,200 files

Hi, It takes 4 to 5 hour to complete the commit of surefire site on SVN. The site is about 4,200 files and 820 folders. I am doing it on people.apache.org machine; otherwise Maven scm-publish would fail on my localhost. Are you facing any SVN feature to take *.tgz archive of surefire-LATEST and

Re: svn commit: r1708587 - in /maven/release/trunk: ./ maven-release-manager/ maven-release-manager/src/main/java/org/apache/maven/shared/release/config/ maven-release-manager/src/main/java/org/apache

On Wed, Oct 14, 2015 at 6:41 PM, Olivier Lamy wrote: > did you create a branch with this change? > At least to help the guys who worked on that... Since it was a single commit, I didn't think it necessary. I could either reapply it to trunk or make a branch; to some extent I'm waiting to hear fr

Re: svn commit: r1708587 - in /maven/release/trunk: ./ maven-release-manager/ maven-release-manager/src/main/java/org/apache/maven/shared/release/config/ maven-release-manager/src/main/java/org/apache

did you create a branch with this change? At least to help the guys who worked on that... On 14 October 2015 at 22:52, wrote: > Author: bimargulies > Date: Wed Oct 14 11:52:53 2015 > New Revision: 1708587 > > URL: http://svn.apache.org/viewvc?rev=1708587&view=rev > Log: > SCM-775: revert the cha

VOTE] Release Apache Maven Shared Archiver 3.0.0

Hi, Note: This is a Maven 3.0 / JDK 6 release We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12333673 There are several issue open: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20ORDER%20BY%

Re: [VOTE] Release Apache Maven Release version 2.5.3

Hi Benson, shasum checked Ok. checked via mvn -Prun-its clean verify Maven 3.0.5, 3.1.1, 3.2.5, 3.3.3 without any issue... so +1 from me... Kind regards Karl Heinz Marbaise On 10/14/15 2:05 PM, Benson Margulies wrote: Hi, We solved 2 issues: Release Notes - Maven Release Plugin - Version

[RESULT] [VOTE] Release Apache Maven Shared Utils 3.0.0 (Take 2)

Hi, The vote has passed with the following result: +1 (binding): Benson Margulies, Olivier Lamy, Jason van Zyl +1 (non binding): Tibor Digana I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise ---

Re: Releasable by default?

Hi, On 10/14/15 2:46 PM, Benson Margulies wrote: On Wed, Oct 14, 2015 at 8:31 AM, Jason van Zyl wrote: I don’t think we need a policy for this, it’s just common sense not to break master. Agreed.. If someone inadvertently makes master not work properly then provide a > reason and put th

Re: Releasable by default?

Replace always working with always releasable. To me it means the same thing. > On Oct 14, 2015, at 8:46 AM, Benson Margulies wrote: > > On Wed, Oct 14, 2015 at 8:31 AM, Jason van Zyl wrote: >> I don’t think we need a policy for this, it’s just common sense not to break >> master. >> >> If so

Re: Releasable by default?

On Wed, Oct 14, 2015 at 8:31 AM, Jason van Zyl wrote: > I don’t think we need a policy for this, it’s just common sense not to break > master. > > If someone inadvertently makes master not work properly then provide a reason > and put that change on a branch. The developer who did it might not h

Re: Releasable by default?

I don’t think we need a policy for this, it’s just common sense not to break master. If someone inadvertently makes master not work properly then provide a reason and put that change on a branch. The developer who did it might not have time at the point someone else finds the issue so anyone ca

Releasable by default?

I'd like to open a discussion of a possible policy. The policy would look something like the following: ___ All of the projects managed by the Maven PMC are maintained in a releasable condition. If a developer wants to make a change that will result in an a component being unreleasable for any s

[VOTE] Release Apache Maven Release version 2.5.3

Hi, We solved 2 issues: Release Notes - Maven Release Plugin - Version 2.5.3 ** Bug * [MRELEASE-921] - perform goal doesn't support providerImplementation * [MRELEASE-925] - Old version of plexus utils forced here causes failures There are still a couple of issues left in JIRA: https: