Looked fine to me when I found it just after writing my version! Merge away!
On Tue 28 Mar 2017 at 20:31, Robert Scholte <rfscho...@apache.org> wrote: > I've created a branch for MNG-6185, ready to be merged. > > Robert > > On Fri, 24 Mar 2017 11:45:14 +0100, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.5.0-candidate%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > > > Here is my opinions: > > > > https://issues.apache.org/jira/browse/MNG-6167 - it's too late now. punt > > to > > 3.5.1 > > > > https://issues.apache.org/jira/browse/MNG-6168 - If this is available > and > > ready quickly (i.e. in the next week), we can review the changes and > > assess > > the risk > > > > https://issues.apache.org/jira/browse/MNG-6186 - looks like not merged > > and > > released upstream yet... punt to 3.5.1 > > > > https://issues.apache.org/jira/browse/MNG-6188 - it's too late now. punt > > to > > 3.5.1 (anyway I see similar issues with other native tooling that uses > > console colouring) > > > > https://issues.apache.org/jira/browse/MNG-6169 - definitely too late. > > punt > > to 3.5.1 > > > > https://issues.apache.org/jira/browse/MNG-6185 - sounds like only a > > javadoc > > change. If available quickly should be ok > > > > If there is agreement then I will move MNG-6185 and MNG-6168 into fix for > > 3.5.0 and the rest to 3.5.1-candidates > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
