You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2018/10/20 09:39:57 UTC
[ANN] Final Call for Maven Core Release 3.6.0
Hi,
As it looks like everything seemed to be in current Master of Maven Core
what should be part of it.
I will give 72h for anyone to surface any issues you wish to claim
should be included in 3.6.0 and have not already been merged.
As the person stepping up to be release manager* for 3.6.0,
I get to decide
if:
* your claim is valid and I will wait for your changes; or whether
* I will go ahead without your changes.
After all blocking changes are merged I will start shake-down to ensure
the build is releasable. This may result in reverts of changes that are
not fully baked or it may mean that we surface a new blocking issue that
we need to wait for.
Once we are ready for a release... we go!
Kind regards
Karl Heinz Marbaise
PS.: Text is shamelessly copied from Stephens announcement.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Final Call for Maven Core Release 3.6.0
Posted by Michael Osipov <mi...@apache.org>.
Am 2018-10-20 um 11:39 schrieb Karl Heinz Marbaise:
> Hi,
>
> As it looks like everything seemed to be in current Master of Maven Core
> what should be part of it.
>
> I will give 72h for anyone to surface any issues you wish to claim
> should be included in 3.6.0 and have not already been merged.
I think Sylwester has a decent fix/PR for MNG-6490. I'll leave it up to
him to merge it.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Final Call for Maven Core Release 3.6.0
Posted by Arnaud Héritier <ah...@gmail.com>.
go go go
On Sat, Oct 20, 2018 at 5:01 PM Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> On Sat 20 Oct 2018 at 10:40, Karl Heinz Marbaise <kh...@gmx.de>
> wrote:
>
> > Hi,
> >
> > As it looks like everything seemed to be in current Master of Maven Core
> > what should be part of it.
> >
> > I will give 72h for anyone to surface any issues you wish to claim
> > should be included in 3.6.0 and have not already been merged.
> >
> > As the person stepping up to be release manager* for 3.6.0,
> >
> > I get to decide
> >
> > if:
> >
> > * your claim is valid and I will wait for your changes; or whether
> > * I will go ahead without your changes.
> >
> > After all blocking changes are merged I will start shake-down to ensure
> > the build is releasable. This may result in reverts of changes that are
> > not fully baked or it may mean that we surface a new blocking issue that
> > we need to wait for.
> >
> > Once we are ready for a release... we go!
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> > PS.: Text is shamelessly copied from Stephens announcement.
>
>
> Go for it!
>
>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > --
> Sent from my phone
>
--
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Re: [ANN] Final Call for Maven Core Release 3.6.0
Posted by Stephen Connolly <st...@gmail.com>.
On Sat 20 Oct 2018 at 10:40, Karl Heinz Marbaise <kh...@gmx.de> wrote:
> Hi,
>
> As it looks like everything seemed to be in current Master of Maven Core
> what should be part of it.
>
> I will give 72h for anyone to surface any issues you wish to claim
> should be included in 3.6.0 and have not already been merged.
>
> As the person stepping up to be release manager* for 3.6.0,
>
> I get to decide
>
> if:
>
> * your claim is valid and I will wait for your changes; or whether
> * I will go ahead without your changes.
>
> After all blocking changes are merged I will start shake-down to ensure
> the build is releasable. This may result in reverts of changes that are
> not fully baked or it may mean that we surface a new blocking issue that
> we need to wait for.
>
> Once we are ready for a release... we go!
>
> Kind regards
> Karl Heinz Marbaise
>
> PS.: Text is shamelessly copied from Stephens announcement.
Go for it!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
Sent from my phone