[DISCUSS] Towards a common understanding of things

We need to define: * what is a bug vs what is an rfe * what are the different severities for bugs and rfes * what severity bugs block: an alpha, a beta, a full release * what do the different release types mean? (My take, alpha is not feature complete, beta is not free of bugs, rc is hopefully

[GitHub] maven-indexer issue #13: MINDEXER-97: Index/Store Extra OSGI Headers

Github user balazs-zsoldos commented on the issue: https://github.com/apache/maven-indexer/pull/13 +1 --- 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

[SUMMARY] [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

On Sat 11 Mar 2017 at 21:56, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: Hi all, I think it is a good thing if we take stock of where we are and how we are doing. I would really appreciate if everyone could take a few minutes to respond with their top three of two areas: * What

Maven Site / Report Plugins

Hi, currently I stumbled over a thing which I don't understand. I have parent pom[1] which defines several parts of a site including some reports for example maven-changes-plugin with github-report.. Now I inherit from that parent pom and of course I can do a mvn site. But now the important

Re: [08/17] maven git commit: [MNG-6182] ModelResolver interface enhancements.

On Sun 19 Mar 2017 at 02:58, Christian Schulte wrote: > Branch name is MNG-6182 > > < > https://git-wip-us.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/MNG-6182 > > > > Commit is > > < >

Re: Distribution file permission issue with current master.

yes, this is a critical bug in fact, I didn't understand your initial report and didn't see that there was an issue with only the .zip distribution file (every other distribution -- that I tried -- does not have this issue, and this jansi-native directory is not different from other directory

[DISCUSS] Planning process for 3.5.1

So planning for 3.5.0 was total chaos... but it seems to have worked. How do we want to work for 3.5.1? (As usual, I have my own ideas but I will hold back until I see some suggestions from others because we are a community and as release manager for 3.5.1 my opinion might be too powerful and we

Re: [DISCUSS] Towards a common understanding of things

Am 19.03.2017 um 13:13 schrieb Stephen Connolly: > We need to define: > > * what is a bug vs what is an rfe > > * what are the different severities for bugs and rfes > > * what severity bugs block: an alpha, a beta, a full release > > * what do the different release types mean? (My take, alpha

[GitHub] maven-indexer issue #13: MINDEXER-97: Index/Store Extra OSGI Headers

Github user sesuncedu commented on the issue: https://github.com/apache/maven-indexer/pull/13 I have been consistently confused about which branch is live, so it would not surprise me either way ☺️. I had been working against main on some code to use the central index to

Re: maven git commit: [MNG-6069] Migrate to non deprecated parts of Commons CLI

Hervé and I were discussing this on IRC... perhaps we can merge this for 3.5.0-beta-1 and if it causes issues then we can revert for 3.5.0 As these are public static final String and char constants, it should not break binary compatibility as javac inlines static final constants... it may break

Re: [DISCUSS] Towards a common understanding of things

Am 19.03.2017 um 13:13 schrieb Stephen Connolly: > We need to define: > > * what is a bug vs what is an rfe I'll give it a try. Everything not working as documented/specified is a bug, when there is consensus the documentation/specification is stating the intended/correct behaviour. The design

Re: [SUMMARY] [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

What marketing can we do in order to hire new developers? In my experience employees are still asking the same question "How much do they pay" ;-) I am still trying to explain that you are improving Maven used in your daily work. I do not want this great project to see dying. It's being widely

Re: seconding MNG-6189: WARN if maven-site-plugin configuration contains reportPlugins element

+1 On Sun 19 Mar 2017 at 16:21, Hervé BOUTEMY wrote: > see https://issues.apache.org/jira/browse/MNG-6189 for more details on the > logic behind this warning. > > It's only a warning, and there is an IT to check the result > > I think it is safe and will help us continue

[GitHub] maven-indexer issue #13: MINDEXER-97: Index/Store Extra OSGI Headers

Github user carlspring commented on the issue: https://github.com/apache/maven-indexer/pull/13 Hi, Shouldn't this be applied to the `master` branch and be included in `6.0` instead? @cstamas : What do you think? Cheers, Martin

[GitHub] maven-indexer issue #13: MINDEXER-97: Index/Store Extra OSGI Headers

Github user sesuncedu commented on the issue: https://github.com/apache/maven-indexer/pull/13 Also, OSGI headers really need a custom analyzer, as they have their own nested organization and datatyping. It doesn't seem worth it for this change, but would be worth it for the next

[GitHub] maven-indexer issue #13: MINDEXER-97: Index/Store Extra OSGI Headers

Github user sesuncedu commented on the issue: https://github.com/apache/maven-indexer/pull/13 Also, if I do forward port, should I also try and forward port index-reader? And, if you are thinking of releasing 5.1.2, would you like me to do a more detailed job of bundle

Re: maven git commit: [MNG-6069] Migrate to non deprecated parts of Commons CLI

Hi, I'm not sure if this for 3.5.0 beta or what ever we call it...at the moment the tests are not working...and I need to dive into it why are failing..it looks there are missing some dependencies..but I'm note sure about it... But it looks you have already decided what to do... Kind

Re: Distribution file permission issue with current master.

Am 19.03.2017 um 10:39 schrieb Hervé BOUTEMY: > I updated parent pom, which brings a new m-assembly-p version that does not > have this bug Thanks. Regards, -- Christian - To unsubscribe, e-mail:

seconding MNG-6189: WARN if maven-site-plugin configuration contains reportPlugins element

see https://issues.apache.org/jira/browse/MNG-6189 for more details on the logic behind this warning. It's only a warning, and there is an IT to check the result I think it is safe and will help us continue cleaning users poms for people lost in stopped migration from to In addition, this

Re: [SUMMARY] [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Tibor, Could you move this to its own thread. Let's keep this retrospective thread closed. It's done it's job Thanks in advance, - Stephen On Sun 19 Mar 2017 at 13:46, Tibor Digana wrote: > What marketing can we do in order to hire new developers? > In my experience

Re: [DISCUSS] Towards a common understanding of things

Please let's keep this for the other thread I am trying to start off. It's really related to how we work with branches and how we use CI (But that is a more complex thread to kick off) So let's keep this thread on topic please On Sun 19 Mar 2017 at 15:59, Christian Schulte

[DISCUSS] How to work with branches

Unlike the other discuss threads, I think I have some extra context that means I am going to start from my proposal... or rather my requirements and then proposal to solve those requirements. Requirements === As a Release Manager, I cannot tell which branches on the CI server are

Re: maven git commit: [MNG-6069] Migrate to non deprecated parts of Commons CLI

Tests are failing because system properties are not being parsed correctly with the new builder based options. It seems that we get for `-Drevision=1.3.0 -Dmaven.local.repo=/foo/bar` when on MavenCli line 1676 we get defStrs == { "revision", "1.3.0", "maven.local.repo", "/foo/bar"} This results

Re: [DISCUSS] How to work with branches

On Sun 19 Mar 2017 at 20:05, Fred Cooke wrote: > How are branches noisy? Promiscuous automated emails or some such? PMC (and committers too, but the buck stops at the PMC) are supposed to monitor the commits@m.a.o mailing list. Every time a branch is rebased... boom all

Re: maven git commit: [MNG-6069] Migrate to non deprecated parts of Commons CLI

If the tests are not working by Monday then it's out on its ear ;-) On Sun 19 Mar 2017 at 18:11, Karl Heinz Marbaise wrote: > Hi, > > I'm not sure if this for 3.5.0 beta or what ever we call it...at the > moment the tests are not working...and I need to dive into it why are >

Re: seconding MNG-6189: WARN if maven-site-plugin configuration contains reportPlugins element

merged to master thank you Hervé Le dimanche 19 mars 2017, 16:35:14 CET Stephen Connolly a écrit : > +1 > > On Sun 19 Mar 2017 at 16:21, Hervé BOUTEMY wrote: > > see https://issues.apache.org/jira/browse/MNG-6189 for more details on the > > logic behind this warning. >

Re: Maven Site vs Reporting Plugin workflows?

as you can read in latest comments on MPDF-48, I prepared in MSHARED-628 maven-reporting-exec code for execution of reports taken from section Does it look clear to you now? Regards, Hervé Le mercredi 15 mars 2017, 20:29:41 CET Alex O'Ree a écrit : > Hervé thanks for the pointer. The

Re: Maven Resolver 1.1

I did some description enhancements in MNG-6182, stating clearly what is the change (even roughly, but more precisely than just telling "enhancement") Please review MNG-6182 and do such factual description in MNG-6183 Regards, Hervé Le jeudi 16 mars 2017, 02:13:42 CET Christian Schulte a

Re: [DISCUSS] How to work with branches

How are branches noisy? Promiscuous automated emails or some such? Surely you don't need to look at all branches unless you've been asked to pre-review something prior to fast-forward? Just the ones you're interested in? Naming scheme sounds sensible, however unless everyone is constantly

Re: maven git commit: [MNG-6069] Migrate to non deprecated parts of Commons CLI

I think I have fixed this issue with b424af57a56a4059763000b87bbe5e4331329b36 On 19 March 2017 at 20:24, Stephen Connolly wrote: > Tests are failing because system properties are not being parsed correctly > with the new builder based options. > > It seems

Re: [DISCUSS] Towards a common understanding of things

for you, documentation is always right? That's the first time I see that documentation is more important and always more accurate than how the tool works If there is a discrepency between how the tool works and what is written in documentation, there is work to be done to define what part has

Re: [DISCUSS] How to work with branches

until now, target version was managed through Jira issue: I'm not convinced putting the info in an additional place like branch name will help keep info in sync For the merge idea, the "target branch" concept seems too much for me: if the branch was automatically locally rebased on master,

Re: [DISCUSS] How to work with branches

No need to cherry-pick, that should be a rare operation. Clean up the branch and prepare it for a fast forward with high quality commits, then just push it when it's ready and passes scrutiny and tests. +1 on ugly masters. Last time I looked at the docker project the displayed history showed 15

Re: Maven Site / Report Plugins

That's the first time I see this part of the doc: defining an empty reportSet could remove a report plugin? I'm not convinced it ever worked. to me, it is inconsistent with following documentation, associated to an IT: http://maven.apache.org/plugins/maven-site-plugin/

[GitHub] maven-indexer pull request #14: MINDEXER-100

GitHub user sesuncedu opened a pull request: https://github.com/apache/maven-indexer/pull/14 MINDEXER-100 Forward port changes from maven-indexer-5.x branch to master. Minor fixes to pom.xml's and test resources. Manually set org.apache.maven.index.reader package version to

[GitHub] maven-doxia pull request #2: Replace module-markdown pegdown parser to flexm...

GitHub user vsch opened a pull request: https://github.com/apache/maven-doxia/pull/2 Replace module-markdown pegdown parser to flexmark-java Java language level for this module is 1.7 You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] Towards a common understanding of things

Am 03/19/17 um 23:32 schrieb Hervé BOUTEMY: > for you, documentation is always right? > That's the first time I see that documentation is more important and always > more accurate than how the tool works > > If there is a discrepency between how the tool works and what is written in >

Re: [DISCUSS] How to work with branches

Am 03/19/17 um 18:34 schrieb Stephen Connolly: > Unlike the other discuss threads, I think I have some extra context that > means I am going to start from my proposal... or rather my requirements and > then proposal to solve those requirements. > > Requirements > === > > As a Release

Re: [DISCUSS] How to work with branches

On Sun 19 Mar 2017 at 23:38, Christian Schulte wrote: > Am 03/19/17 um 18:34 schrieb Stephen Connolly: > > Unlike the other discuss threads, I think I have some extra context that > > means I am going to start from my proposal... or rather my requirements > and > > then proposal

Re: [DISCUSS] How to work with branches

On Sun 19 Mar 2017 at 22:56, Fred Cooke wrote: > No need to cherry-pick, that should be a rare operation. > > Clean up the branch and prepare it for a fast forward with high quality > commits, then just push it when it's ready and passes scrutiny and tests. > > +1 on ugly

Re: [DISCUSS] Towards a common understanding of things

On Sun 19 Mar 2017 at 12:13, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > We need to define: > > * what is a bug vs what is an rfe > > * what are the different severities for bugs and rfes > S1: software is unusable, halts, crashes, or is inaccessible, resulting in a critical

Re: [DISCUSS] How to work with branches

Sounds like the solution is for people to use a different remote that you don't feel personally responsible for checking every commit in. And to fix the email system. Split emails for commits on master to everyone and a new list for other branches. As for Jenkins validating a merge, that's

Re: [DISCUSS] Towards a common understanding of things

Am 03/20/17 um 01:11 schrieb Stephen Connolly: > On Sun 19 Mar 2017 at 12:13, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> We need to define: >> >> * what is a bug vs what is an rfe >> >> * what are the different severities for bugs and rfes >> > > S1: software is unusable,

Re: [DISCUSS] Towards a common understanding of things

Am 03/20/17 um 01:47 schrieb Christian Schulte: > Am 03/20/17 um 01:11 schrieb Stephen Connolly: >> On Sun 19 Mar 2017 at 12:13, Stephen Connolly < >> stephen.alan.conno...@gmail.com> wrote: >> >>> We need to define: >>> >>> * what is a bug vs what is an rfe >>> >>> * what are the different

Re: [DISCUSS] Planning process for 3.5.1

Am 03/19/17 um 12:43 schrieb Stephen Connolly: > So planning for 3.5.0 was total chaos... but it seems to have worked. > > How do we want to work for 3.5.1? We need to answer all the other questions first (versioning, bug vs. feature, branches, etc.). Question is: How to decide which

Re: [DISCUSS] How to work with branches

Just two cents from a long-time list lurker: First, congrats on all the work done so far! Monumental effort, and a well-deserved congratulations to everyone involved. As a Release Manager, > > I cannot tell which branches on the CI server are targeted for the release > and which are "future

Re: [DISCUSS] How to work with branches

On Sun, Mar 19, 2017 at 6:56 PM, Fred Cooke wrote: > No need to cherry-pick, that should be a rare operation. > > Clean up the branch and prepare it for a fast forward with high quality > commits, then just push it when it's ready and passes scrutiny and tests. > I agree,