Hi to all,
I would like to start with the release on Thursday evening.
If there are any objections please rais your hands...
Kind regards
Karl Heinz Marbaise
On 01.04.19 23:42, Dan Tran wrote:
MNG-6605 indeed is a good one to have
On Mon, Apr 1, 2019 at 12:08 AM Karl Heinz Marbaise <[email protected]>
wrote:
Hi Michael,
On 01.04.19 08:54, Michael Osipov wrote:
Am 2019-03-31 um 21:36 schrieb Karl Heinz Marbaise:
Hi,
I would like to collect the issues which should be part of Maven 3.6.1:
MNG-6605 will go into. Non-intrusive, not active by default.
I've seen that...that's good idea...
On 31.03.19 21:27, Karl Heinz Marbaise wrote:
Hi Michael,
would it be helpful if I start the release tomorrow ?
Cause I can see the list of issues assigned to Maven 3.6.1 is solved
the
status looks Ok to me.
Kind Regards
Karl Heinz Marbaise
On 31.03.19 21:10, Mickael Istria wrote:
Hi,
What's the status of the release? Is its backlog «closed» now? When
is it
supposed to be shipped?
I'd like to make sure Eclipse m2e can upgrade before next released
as the
was already dalyed once.
Cheers,
On Saturday, March 23, 2019, Hervé BOUTEMY <[email protected]>
wrote:
there is only one task to do: transform the great minimal testcase
provided in
https://issues.apache.org/jira/browse/MNG-6506 to an IT, to not just
upgrade
blindly a dependency but keep track of what it solves
Regards,
Hervé
Le vendredi 22 mars 2019, 11:45:19 CET Roman Grigoriadi a écrit :
What is the issue with including MNG-6543 and MNG-6506?
plexus-classworlds 2.6.0 seems to have a fix for both of them, are
there
any integration failures?
Roman
On Fri, Mar 22, 2019 at 9:32 AM Karl Heinz Marbaise
<[email protected]>
wrote:
Hi,
On 22.03.19 09:25, Michael Osipov wrote:
Am 2019-03-22 um 08:37 schrieb Mickael Istria:
Hi,
On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY
<[email protected]
wrote:
We're working on it, it should happen quite soon, but no date is
really
guaranteed: as you can see from Jira issues to be resolved [1],
we're
near...
At this point, since there are some blockers issues that have
been
fixed
and community is in need of the new release, shouldn't we avoid
adding
enhancements in 3.6.1 backlog, focus on important remaining
bugs and
try to
ship it ASAP?
It seems to me that the scope of 3.6.1 is always growing, at the
risk
of
never releasing a lot of value that was already produced...
I agree, I'd move out MNG-6506 and MNG-6543 and continue with the
relase.
@Karl, can you make MNG-6538 happen?
I will in the evening...already assigned the ticket...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
