Am 2017-02-11 um 15:33 schrieb Robert Scholte:
The list of updates should be added to the release notes, I'd say use
the matching JIRA issue.
Do you want me to add these to the issue description itself? Unless I
create a JIRA issue per dependency, they won't show up in the release
notes. One could do this with sub-tasks.
branch of MNG-5967 looks good to me.
Thanks, I will merge when all tests pass.
I have now added a MNG-5968 branch, but I think this needs to be broken
up into three separate issues:
1. Lifecycle/binding plugin version updates
2. Super POM plugin version updates
3. Default plugin version updates
WDYT?
On Sat, 11 Feb 2017 15:30:46 +0100, Michael Osipov <micha...@apache.org>
wrote:
Am 2017-02-11 um 15:18 schrieb Robert Scholte:
In both cases I'm missing a list of what's being updated (and maybe
why...).
I know there were a couple of plugins for which the latest is not the
greatest due to some small regressions.
So without these details I'd say no.
I am preparing two branches based on Christian's work, so you'll see
what will end up in the merge. No secrets here.
On Sat, 11 Feb 2017 12:06:34 +0100, Michael Osipov <micha...@apache.org>
wrote:
Am 2017-02-08 um 21:14 schrieb Michael Osipov:
Am 2017-02-08 um 21:01 schrieb Stephen Connolly:
I think all the important stuff is merged. I'll take a final review
through
and then cut alpha-1
We can still add stuff if necessary for an alpha-2 but I'd much
prefer to
focus that on shaking out bugs.
Ideally we do at most 3 alpha's before soft-code-freeze and a beta
(at
which point it should only be serious bug fixes)
Then we give the beta some soak and cut the release
I toyed with spinning RCs but I'm thinking alpha and beta are better
terms
Looks good to me. I think that the very first alpha should also
include
MNG-5967 Dependency updates
MNG-5968 Default plugin version updates
as well as this cheap, non-functional improvement:
MNG-5934 String handling issues identified by PMD
If Christian is busy, I can take on them.
Christian,
do you mind to merge them into master? If you won't can I take over?
Anyone else seconding those issues?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
