+1
On Fri, 13 Jan 2017 12:34:48 +0100, Robert Scholte
wrote:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12338627&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=projec
great!
I like it :)
Regards,
Hervé
Le samedi 14 janvier 2017, 13:39:47 CET rfscho...@apache.org a écrit :
> Author: rfscholte
> Date: Sat Jan 14 13:39:47 2017
> New Revision: 1778770
>
> URL: http://svn.apache.org/viewvc?rev=1778770&view=rev
> Log:
> [MPLUGIN-319] @since values ignored in r
yes, this is currently for 3.5.0 that this fix should be in, then with this
seconding principle
once Maven 3.5.0 is out, we'll need to define if we continue that way or not
Regards,
Hervé
Le samedi 14 janvier 2017, 12:24:09 CET Stephen Connolly a écrit :
> The "seconding" thing was from my per
The "seconding" thing was from my perspective just a 3.5.0 thing...
If people like it, fine. But it might be a bit much as a project culture
On Sat 14 Jan 2017 at 03:42, Hervé BOUTEMY wrote:
> > This also brings me to another point: could somebody second MNG-6109[2]
>
> > for M3.5.0, so I can l
I suggest confirming it on the original thread so all the decisions are
easier to trace back
Robert
On Sat, 14 Jan 2017 04:40:02 +0100, Hervé BOUTEMY
wrote:
This also brings me to another point: could somebody second MNG-6109[2]
for M3.5.0, so I can lock the Maven version in the maven-pl
Hervé
How are we doing?
--
Sent from my phone
Once we establish a pattern for merging the 3.5.0 target changes, I should
hopefully be able to get out of the way... but for now - as release manager
- I just want to ensure everyone knows that their changes must pass on a
Maven-Jenkinsfile branch build first
On Sat 14 Jan 2017 at 04:07, Hervé BO
