Dear Apache Maven Community,
Recently, in a discussion within the PMC, we discovered a complete
misconception about release votes: a lot of people feel that voting on
releases is not useful if you are not in the PMC. That's wrong!
After digging into the issue, we found that a few years ago, whe
Hi, i have prepared an announcement mail content and want to know if
this would be ok...I would also emphasize the naming of
contributor/reports
WDYT ?
=== START ==
The Apache Maven team is pleased to announce the release of
Apache Maven 3.3.7.
FYI Mark, your vote is binding as a contributor... i.e. if you voted
-1 the release manager would have to consider aborting the release,
your vote just does not provide one of the three required +1's by PMC
members required to invoke the foundation legal protections for
contributors.
(A release ma
Hi,
just a note on this conclusion which remembers me that we should add
those cotributors to the final announcment mail and put them on the
release notes as well...to give them the credit they deserve instead of
only mention them here on the dev list...
BTW: Thanks to Stephen to summarize t
The Apache Maven team is pleased to announce the release of the
Apache Maven Shade Plugin Version 2.4.2.
This plugin provides the capability to package the artifact in an uber-jar,
including its dependencies and to shade - i.e. rename - the packages of some of
the dependencies.
https://maven.apac
On 29 Oct 2015, at 2:30, Jason van Zyl wrote:
> Time to release Maven 3.3.7!
+1 non-binding. Works fine on our builds using heavy maven-tiles, and my
largish IT test project all works fine.
Been doing releases and builds all day with no issue.
Mark
--
Mark Derricutt
http://www.theoryinprac
Thanks very much for cleaning up JIRA.
jvz
> On Oct 28, 2015, at 2:11 PM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> I have cleaned up JIRA ...moved all not solved issues to Backlog for 3.X
>
> Furthermore checked with several projects...maven-jar-plugin,
> maven-assembly-plugin (current trunk),
Sure you can close the PR. Put 'Closes #nn.' in a commit message.
On Oct 28, 2015 4:38 PM, "Stephen Connolly"
wrote:
> I
>
> On Wednesday 28 October 2015, Michael Osipov wrote:
>
> > Am 2015-10-28 um 18:28 schrieb Stephen Connolly:
> >
> >> Thanks for contributions from non-committers go to:
> >
Hi,
I have cleaned up JIRA ...moved all not solved issues to Backlog for 3.X
Furthermore checked with several projects...maven-jar-plugin,
maven-assembly-plugin (current trunk), some of my own projects
(uptodate-maven-plugin, iterator-maven-plugin, test-maven-eventspy etc.)
without any issue.
I
On Wednesday 28 October 2015, Michael Osipov wrote:
> Am 2015-10-28 um 18:28 schrieb Stephen Connolly:
>
>> Thanks for contributions from non-committers go to:
>> * Martin Schäf
>> * Joseph Walton
>> * Keith Turner
>> * Anton Tanasenko
>> * Stephen Kitt
>> * "tssp at web dot de" (whoever you
Hi,
The vote has passed with the following result:
+1 (binding): Tibor Digana, Olivier Lamy,
Karl Heinz Marbaise, Benson Margulies
+1 (non binding): Uwe Barthel
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
---
Am 2015-10-28 um 14:30 schrieb Jason van Zyl:
Hi,
Time to release Maven 3.3.7!
Here is a link to the issues resolved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074
Staging repo:
https://repository.apache.org/content/repositories/maven-1228/
The dis
Am 2015-10-28 um 18:28 schrieb Stephen Connolly:
Thanks for contributions from non-committers go to:
* Martin Schäf
* Joseph Walton
* Keith Turner
* Anton Tanasenko
* Stephen Kitt
* "tssp at web dot de" (whoever you are - a small commit with clear
intent of Apache License grant)
* "sugartxy " (o
Here is my vote:
* As a community member on the technical merit of making this specific release
+1: I have tested this build on the projects that I know are
troublesome and the regressions in 3.3.1 and 3.3.3 are resolved.
* As a member of the committee established by the ASF board with
responsib
+1
Robert Scholte
My point, if I was unclear my apologies, was that the backlog should just
be where work is to be found. And if you find work, then move it into the
next release version. I think that's a simple "one-stop shopping" way to
look at this. It's just a suggestion I thought could help.
Cheers,
Paul
On
If I put them in the backlog I will completely forget about them. If someone
else wants to shuffle the issues go for it.
jvz
> On Oct 28, 2015, at 7:32 AM, Paul Benedict wrote:
>
> FYI, 14 unresolved issues need to move to 3.3.x to make the JIRA list
> correct.
>
> PS: Instead of moving the u
FYI, 14 unresolved issues need to move to 3.3.x to make the JIRA list
correct.
PS: Instead of moving the unresolved forward to a 3.3.8 bucket, how come
they aren't put in the Backlog? It would save churn. The Backlog should be
cherry-picked and tickets pulled into the next release when work is rea
Hi,
Time to release Maven 3.3.7!
Here is a link to the issues resolved:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074
Staging repo:
https://repository.apache.org/content/repositories/maven-1228/
The distributable binaries and sources for testing can
19 matches
Mail list logo
