Am 03/04/17 um 14:56 schrieb Stephen Connolly:
> We are still in alpha, so bugs with severity S1-S3 are eligible (and S4
> with a risk assessment)
> Severity is something like this (but as a project we probably need to
> define the categories for Maven core)
>
> S1: blows up for everyone, no worka
Am 03/04/17 um 18:54 schrieb Hervé BOUTEMY:
> I have one question, which is recurring for every issue: what is the impact?
>
> I understand the logic: it should fix a bug (that is told introduced in Maven
> 3.3.1), and the bug is explained by the logic behind the javadoc.
> But no pointer to any
Am 03/04/17 um 18:54 schrieb Hervé BOUTEMY:
> I have one question, which is recurring for every issue: what is the impact?
>
> I understand the logic: it should fix a bug (that is told introduced in Maven
> 3.3.1), and the bug is explained by the logic behind the javadoc.
> But no pointer to any
I have one question, which is recurring for every issue: what is the impact?
I understand the logic: it should fix a bug (that is told introduced in Maven
3.3.1), and the bug is explained by the logic behind the javadoc.
But no pointer to any code using this method, and that shows that Maven 3.3.
I've created two more issues:
MNG-6181 Wagon produces a lot of noise at debug loglevel
MNG-6180 groupId has plain color when goal fails
I have no proper solution yet for MNG-6181, maybe we simply need to change
the loglevel for wagon to INFO.
Robert
On Sat, 04 Mar 2017 02:45:21 +0100, Hervé
Hi,
I see it the same way...I think we might need an alpha-2 but then I
don't a requirement for further releases before the final GA...
I would like to get two changes into alpha-2 (MNG-6057, MNG-6170) which
fixing things.
MNG-6170 fixes an edge case in relationship with -T XX calling a goal
We are still in alpha, so bugs with severity S1-S3 are eligible (and S4
with a risk assessment)
Severity is something like this (but as a project we probably need to
define the categories for Maven core)
S1: blows up for everyone, no workaround
S2: blows up under certain circumstances, no workarou
Am 03/02/17 um 22:55 schrieb Stephen Connolly:
> I'd like to declare feature freeze for alpha-2 on March 9th.
>
> If a feature does not land in alpha-2 it will not be in beta-1 (i.e. Only bug
> fixes or rip out features that are causing S1/S2 issues will be in the diff
> from alpha-2 to beta-1)
1 non-final then the final, *if everything happens as expected*: ok, fine for
me,
I can live with that extra step :)
Le samedi 4 mars 2017, 08:12:35 CET Stephen Connolly a écrit :
> I was only planning 1 beta.
>
> And if alpha-2 is good enough and we are confident we can skip the beta...
>
> I
GitHub user cboehme opened a pull request:
https://github.com/apache/maven-integration-testing/pull/19
[MNG-6173] MavenSession.getAllProjects() should return all projects in the
reactor
Integration tests for issue
[MNG-6173](https://issues.apache.org/jira/browse/MNG-6173) as reques
I was only planning 1 beta.
And if alpha-2 is good enough and we are confident we can skip the beta...
I want to avoid RCs, we should have one take only for the actual release
On Sat 4 Mar 2017 at 01:47, Hervé BOUTEMY wrote:
> sorry to open such discussion, but given the good feedback on alpha
11 matches
Mail list logo
