Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

I like this idea of avoiding force pushing, but I'm not git expert to know exactly if this gives exactly the intended result = start clean and not have noise when doing bisects or git blame this technical discussion should probably on a separate email thread, to not pollute the vote thread

Re: FOSDEM 2017

I might come on Sunday. On Thu, 5 Jan 2017 at 14:20, Robert Scholte wrote: > Hi, > > > > Just like the last couple of years FOSDEM has been a great opportunity to > > meet several Maven developers. > > Some of the new features and improvements started here when the Maven

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 Le dim. 8 janv. 2017 à 05:48, Tibor Digana a écrit : > +1 > > > > On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly < > > stephen.alan.conno...@gmail.com> wrote: > > > > > Hi, > > > > > > We have collectively managed to mess up our ability to follow the > original

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 (committer & PMC) notice that the merge ours implementation strategy may be a better implementation than force push with branches renaming If some git expert can dig into implementaion strategies, please, that would be great what is important to me is the vote to reset and to define the

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 On Wed, 4 Jan 2017 at 17:39, Manfred Moser wrote: > +1 (committer) > > > > Stephen Connolly wrote on 2017-01-04 04:16: > > > > > Hi, > > > > > > We have collectively managed to mess up our ability to follow the > original > > > release plan for 3.4.0 which was

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

If we were *throwing away* the other commits then that would work. But as I understand it, ours would mean that the commits are part of the history, so merging would not apply them... tooling to check if they need to be cherry picked would show as already merged... I'd need to check if cherry

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

Hi, +1 (PMC + Committer) Kind regards Karl Heinz Marbaise On 08/01/17 05:48, Tibor Digana wrote: +1 On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: Hi, We have collectively managed to mess up our ability to follow the original release plan for

[GitHub] maven-release pull request #9: Fix for MRELEASE-976

Github user asfgit closed the pull request at: https://github.com/apache/maven-release/pull/9 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 On Sun, 8 Jan 2017 at 6:40 pm, Karl Heinz Marbaise wrote: > Hi, > > > > +1 (PMC + Committer) > > > > Kind regards > > Karl Heinz Marbaise > > > > On 08/01/17 05:48, Tibor Digana wrote: > > > +1 > > > > > > On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly < > > >

[GitHub] maven-release pull request #9: adds project version policies support to rele...

GitHub user hgschmie opened a pull request: https://github.com/apache/maven-release/pull/9 adds project version policies support to release:branch You can merge this pull request into a Git repository by running: $ git pull https://github.com/hgschmie/maven-release

[GitHub] maven-release pull request #8: Fix for MRELEASE-975

GitHub user hgschmie opened a pull request: https://github.com/apache/maven-release/pull/8 Fix for MRELEASE-975 fixes https://issues.apache.org/jira/browse/MRELEASE-975 When passing in an unknown project version policy id with -DprojectVersionPolicyId, the plugin will

[DISCUSS] Stop allowing forced pushes to GIT repositories.

Hi, subject says it all. I'd like to request that our GIT repositories are setup in a way that a 'git --force push' is not possible. Not pulling changes of others in and then force pushing to exchange the remote master branch with some other branch should not be possible. In fact, in subversion

Re: [DISCUSS] Stop allowing forced pushes to GIT repositories.

+1. It should be forbidden on master. Le dim. 8 janv. 2017 à 23:56, Stephen Connolly < stephen.alan.conno...@gmail.com> a écrit : > Master is supposed to be set up that way by infra... if some repositories > > are not set up that way we should just get infra to fix it > > > > On Sun 8 Jan 2017

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 (Committer) Special thanks for pulling all these together -D On Sun, Jan 8, 2017 at 1:05 PM, Olivier Lamy wrote: > +1 > > On Sun, 8 Jan 2017 at 6:40 pm, Karl Heinz Marbaise > wrote: > > > Hi, > > > > > > > > +1 (PMC + Committer) > > > > > > > > Kind

Re: [DISCUSS] Stop allowing forced pushes to GIT repositories.

Master is supposed to be set up that way by infra... if some repositories are not set up that way we should just get infra to fix it On Sun 8 Jan 2017 at 22:47, Christian Schulte wrote: > Hi, > > > > subject says it all. I'd like to request that our GIT repositories are > >

[GitHub] maven-release pull request #8: Fix for MRELEASE-975

Github user asfgit closed the pull request at: https://github.com/apache/maven-release/pull/8 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: Cannot edit or comment on Wiki pages

Hi, I just got "Space Admin" karma to see what happens: edit right are put on maven-committers group, and you are on the Unis maven group https://people.apache.org/phonebook.html?unix=maven Perhaps there is a sync issue between LDAP goups and Confluence groups. Can you confirm that you can't