Hi,
The vote has passed with the following result:
+1 : Tibor Digana, Olivier Lamy, Sylwester Lachiewicz, Hervé Boutemy,
Vida Brevik, Karl Heinz Marbaise
PMC quorum: reached.
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
--
I have advanced the PoC a bit more by adding an experiments mechanism.
To use the dynamic phases PoC you now need to:
1. Build and install Maven on the branch
2. Add the experiments extension in .mvn/extensions.xml, e.g.
http://maven.apache.org/EXTENSIONS/1.0.0"; xmlns:xsi="
http://www.w3.org/2
Hi,
+1 (non binding)
- Built and Tested on Mac from sources
- used the staged binaries to build some big project but without extensions
- works very well with Apache NetBeans 11.x
All looks good, I just want to report this case:
I am running the ITs (current mater) against the staged sources, us
+1 (non binding)
- Built some projects and plugins.
- Built current maven 3.7.0-SNAPSHOT and core ITs.
Environment:
Java version: 1.8.0_222, vendor: AdoptOpenJDK, runtime:
/home/gabriel/.sdkman/candidates/java/8.0.222.hs-adpt/jre
Default locale: es_AR, platform encoding: UTF-8
OS name: "linux", v
The scheme was changed because the users could assign the release version.
Probably there was this change regarding closing the issues.
If you enable them to close the issues, pls make sure that they would not
be able to assign the release while closing.
The users may not be able to evaluate the re
Here's an example of an issue I reported and can't close:
https://issues.apache.org/jira/browse/MNGSITE-368
This issue isn't ready to be closed yet, but if it were I couldn't do
it. By contrast, issues I've reported in Jira against Beam have a
"Close Issue" button that is missing from issues I've
Tested on few projects with no issue
+1
On Fri, Nov 22, 2019 at 8:41 AM Tamás Cservenák wrote:
> +1
>
> On Thu, Nov 21, 2019 at 9:06 PM Robert Scholte
> wrote:
>
> > Hi,
> >
> > This will be a regression release based on some critical issues
> discovered
> > in Maven 3.6.2
> >
> > We solved 10
