Le dimanche 8 mars 2015 16:17:39 Dennis Lundberg a écrit :
> On Sat, Mar 7, 2015 at 1:06 PM, Hervé BOUTEMY <[email protected]
<javascript:;>> wrote:
> >> There is nothing stoping you from releasing 3.3.0 on Java 6 now,
and
> >> 3.4.0
> >> on Java 7 in a few weeks.
> >
> > what I don't like with this plan is that it is exactly what happened
with
> > 3.1.1 then 3.2.1: we never did any bugfix for 3.1.1, 3.1.1 was a
dead
> > branch for start. 3.2.2 bugfixes could/should have been backported
to
> > 3.1.1, but who will ever do that? (not me...)
>
> That is the normal state in open source software. Not many people will
> volunteer to backport bugfixes to older release lines. It's a matter
> of putting your limited resources where it does most good, and also
> where your itch is. Usually this means working on HEAD.
>
> > I agree that the lack of schedule can be a problem if we decide to
make
> > the
> > release this week-end: but if we take one week to integrate Java 7
> > improvements (ie mostly syntax for better maintainability and a few
new
> > APIs) and take one week after that to test the result, IMHO we get a
> > better plan: a new Maven version, with features and the assurance
we'll
> > do bugfix releases on it (the fact that it has upgraded Java
requirement
> > is just a fact on release notes)
>
> I'm not concerned that switching to Java 7 will introduce any new bugs
> in core, at least not until we start using new Java 7 features.
>
> What we should do is think about what is best for our users. Let's
> look at the pros and cons of the two alternatives:
>
> 1. Switch to Java 7 for Maven 3.3.0
>
> Bad: Users that are restricted to Java 6 for some reason will not be
> able to benefit from the bug fixes and new features in 3.3.0
> Good: One less release to make
Good: people (few?) who really need new Maven features on old Java will
learn
to use Toolchains
>
> 2. Switch to Java 7 for Maven 3.4.0
>
> Bad: One more release to make
> Good: Users that are restricted to Java 6 for some reason will benefit
> from the bug fixes and new features in 3.3.0, even though they might
> not get any more bugfixes on that release line, because work focus
> move to 3.4.0-SNAPSHOT as soon as 3.3.0 has been released
>
> > Regards,
> >
> > Hervé
> >
> > Le samedi 7 mars 2015 12:04:15 Dennis Lundberg a écrit :
> >> Hi Kristian,
> >>
> >> Please note that I am not opposed to using Java 7 in the core.
What I
am
> >> objecting to is the planning, or rather the lack of it.
> >>
> >> We currently have core ready to be released on Java 6. Then just
before
> >> it
> >> is about to be released someone says, hey lets switch Java
version as
> >> well. IMO that is something you should plan for before work is even
> >> started
> >> on the next release.
> >>
> >> Then there is the agreement we made regarding Java versions and
their
> >> EOL.
> >>
> >> Switching to Java 7 before the release will mean that a fewer
number
of
> >> users will be able to reap the benefits of the bugfixes and
features
in
> >> Maven 3.3.0.
> >>
> >> There is nothing stoping you from releasing 3.3.0 on Java 6 now,
and
> >> 3.4.0
> >> on Java 7 in a few weeks.
> >>
> >> Weighing in all of this I don't see any reason to change the Java
version
> >> for 3.3.0.
> >> Den 6 mar 2015 13:54 skrev "Kristian Rosenvold" <
> >>
> >> [email protected] <javascript:;>>:
> >> > I already have the full jdk7 port in a branch in github, so that
> >> > assumption
> >> > does not hold :)
> >> >
> >> > Kristian
> >> >
> >> > 2015-03-06 13:50 GMT+01:00 Dennis Lundberg <[email protected]
<javascript:;>>:
> >> > > Hi,
> >> > >
> >> > > If we are going to release 3.3.0 very soon, like this week or
the
> >> > > next, there won't be any time to start using Java 7 features in
the
> >> > > 3.3.0 release. Therefor I would prefer to go with Java 6 for
3.3.0
> >> > > and
> >> > > announce, in the 3.3.0 release notes, that the 3.3.x line is
the
last
> >> > > line that will work with Java 6. Depending on what the core
> >> > > developers
> >> > > want to focus on after the 3.3.0 release is done, the core can
either
> >> > > go 3.3.1-SNAPSHOT with Java 6 or 3.4.0-SNAPSHOT with Java 7.
This
> >> > > would also be consistent with our policy [1] for
plugins/components
> >> > > wanting to move to a higher major Java version, in that we
should
> >> > > release what we currently have in trunk before upgrading to a
higher
> >> > > major Java version.
> >> > >
> >> > > My votes are:
> >> > > -1 for Java 7 in 3.3.0
> >> > > +1 for Java 7 in 3.4.0
> >> > >
> >> > >
> >> > > [1] http://maven.apache.org/developers/java6.html
> >> > >
> >> > > On Thu, Mar 5, 2015 at 1:19 PM, Igor Fedorenko <
[email protected] <javascript:;>>
> >> > >
> >> > > wrote:
> >> > > > With maven core version change to 3.3.0 on master, any
objections I
> >> > > > change compile source/target to java 7?
> >> > > >
> >> > > > --
> >> > > > Regards,
> >> > > > Igor
> >> > > >
> >> > > >
-------------------------------------------------------------------
> >> > > > --
> >> > > > To unsubscribe, e-mail: [email protected]
<javascript:;>
> >> > > > For additional commands, e-mail: [email protected]
<javascript:;>
> >> > >
> >> > > --
> >> > > Dennis Lundberg
> >> > >
> >> > >
---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: [email protected]
<javascript:;>
> >> > > For additional commands, e-mail: [email protected]
<javascript:;>
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
<javascript:;>
> > For additional commands, e-mail: [email protected]
<javascript:;>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] <javascript:;>
For additional commands, e-mail: [email protected]
<javascript:;>
