mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trustin Lee" <trus...@gmail.com>
Subject Re: Is it JDK 1.5 time yet?
Date Sat, 07 Oct 2006 04:17:27 GMT
On 10/7/06, Alex Karasulu <aok123@bellsouth.net> wrote:
>
> Trustin Lee wrote:
> > On 10/7/06, Emmanuel Lecharny <elecharny@gmail.com> wrote:
> >>
> >> John E. Conlon a écrit :
> >>
> >> >Now that the trunk has moved to 1.1.0 do we still plan to move to JDK
> >> >1.5 (and remove the backport-util-concurrent dep)?
> >> >
> >> >regards,
> >> >
> >> >John
> >> >
> >> >
> >> Well, not yet...
> >>
> >> 1.1.0 will still have to keep a jdk 1.4 compatibility, while 2.0 will
> be
> >> full java 5.
> >
> >
> > My and Peter's idea is to move to Java 5 in 1.1.0, which is a unstable
> > branch and to make 1.2 the first stable branch with full Java 5
> > support.  Of
> > course, 1.0.x will be maintained until 1.2 is released.  We can call 1.2as
> > '2.0', but it's just a number.
>
> A major version change says something to users.  Normally it means you
> are breaking with API in a drastic sort of way where backwards
> compatibility is no longer supported.  Minor version changes says that
> things have changed but you can expect most things to be backwards
> compatible.
>
> IMO a break with 1.4 should be done in a major version.
>
> > There are some discussion about having an intermediate version (1.5 ?)
> >> like tomcat did for version 5.5, but they are just discussions.
> >
> >
> > 1.1.x is the intermediate version that experiments Java 5 feature.
>
> I guess you're talking about MINA here and not ApacheDS.
>
> > You have to keep in mind that many prokect are still using a 1.4 jdk,
> >> even if java 5 is becoming more and more visible. Geronimo is still
> >> using a 1.4 jfk, for instance.
> >
> >
> > Moving to 1.2 will take quite a long time as we did for 1.0.  So you can
> > keep using 1.0.x if you want to use MINA in JDK 1.4.  People who wants
> to
> > use Java 5 support can use unstable releases taking a little risk of new
> > experimental features which can be removed when we release 1.2.
>
> Again you should send a clear message to users if you're going to break
> with JDK 1.4.  A bump in the minor number is not sufficient.


OK.  I think we need to provide a nice and flawless versioning scheme that
could be accepted by wide variety of users and developers.  Stay tuned!

Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message