I agree with Arnaud: I'm still having trouble with a 3.1 due to the small
number of really impressive changes, but the majority has decided to make
it 3.1 [1]
-Robert
[1] http://markmail.org/message/7rvio4c5addzkmo4
Op Wed, 28 Nov 2012 17:35:02 +0100 schreef Jason van Zyl <ja...@tesla.io>:
Note that I wasn't in favour of calling this 3.1.x. There are no user
facing features per se but it is an important release, I believe,
architecturally.
I think it's more important to get the momentum back. We were once
releasing every six weeks and getting that swing back gets us more
features for users. But I would be leery of trying to jam in a bunch
user features when we have lost that momentum. There are still 700 or so
bugs in JIRA, we lost one of the most important testing facilities in
the embedded ITs, and I believe the ITs setup is generally flaky. I
don't believe it's wise to try to provide higher level visibility in the
form of new features when we have some lower level problems. Not
releasing for 11 months is rather emblematic of that.
I, at the very least, plan to try and push out two or three more
releases on a 6 week schedule. With a primary focus on making the ITs
run in less than a minute, by whatever means necessary and trying to
drive the issue count down.
On Nov 28, 2012, at 11:04 AM, Arnaud Héritier <aherit...@gmail.com>
wrote:
+0
I found no technical regression but I see really few interest in this
release for now.
It is a minor version (due to some technical changes like in 3.0) while
there are only few bug fixes and nothing new interesting for end users.
I'm not against bug fixes releases but in that case we may have tried
to at
least include something more interesting for end users (like the colored
console from olamy's branch -
https://github.com/aheritier/maven-3/tree/log4j2 - or to fix some real
annoying issues like aether rejecting artifacts from the local
repository
when we change the mirror id in settings or when a remote repo isn't
available anymore - like when you move artifacts betweens staging
repos).
It's dead to justify this release in the name of the "release early,
release often strategy" after 11 months thus we may have waited more
weeks
to have something more interesting.
Thus nothing against it, but nothing in favor of it and I find that sad
for
end-users.
But anyway, thx for the release and to all people involved in it.
Cheers,
Arnaud
On Wed, Nov 28, 2012 at 3:32 PM, Tony Chemit <che...@codelutin.com>
wrote:
On Sun, 25 Nov 2012 22:24:00 -0800
Jason van Zyl <ja...@tesla.io> wrote:
+1 (nb)
Works fine on our projects (nuiton.org, chorem.org) and also on some
codehaus mojo.
thanks,
tony.
Hi,
Here is a link to Jira with 30 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
Staging repo:
https://repository.apache.org/content/repositories/maven-073/
The distributable binaries and sources for testing can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/
Specifically the zip, tarball, and source archives can be found here:
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.zip
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-bin.tar.gz
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.zip
https://repository.apache.org/content/repositories/maven-073/org/apache/maven/apache-maven/3.1.0/apache-maven-3.1.0-src.tar.gz
Staging site:
http://people.apache.org/~jvanzyl/staged-sites/ref/3.1.0
The documentation specifically for this release pertains to JSR330 and
SLF4J-based logging:
http://maven.apache.org/maven-jsr330.html
http://maven.apache.org/maven-logging.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more
examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Tony Chemit
--------------------
tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aherit...@gmail.com
Twitter/Skype : aheritier
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of
dogmas or goals, it's always because these dogmas or
goals are in doubt.
-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
