Many people have been asking if and when we are planning to remove the
Java 1.4 backwards compatibility requirement (BCR). I've mentioned in
previous mails that most of the SIP Communicator developers are just as
eager to get there as anyone else, and now I think that we could almost
put a date on the move.
I have just added "Moving to Java 1.5" as a milestone for the alpha3
release. One of the main reasons for not doing this earlier is the
reports about compatibility problem with JMF, however, now that we are
working on replacing it with FMJ (another alpha3 milestone), we could
afford to drop that 1.4 BCR.
What does this mean in terms of time?
We will probably start preparing the alpha2 release right after the end
of GSoC so that we could roll it out until the end of October (the idea
is to be able and add as much GSoC code in it as possible). Right after
this, two things are going to happen:
1. Developers would be allowed to use J1.5 semantics such as generics
2. We would have to go through most of the existing services and make
sure that we make uniform use of J1.5 semantics (or in other words - do
a face lift on existing code).
By the alpha3 release, which should be out _at_most_ 6 months after
alpha2 (but preferably before the end of February 2008), we should be a
happy 1.5 project.
Right now these are only milestones in the roadmap and we could change
and adjust them as we find fit, so I'd be very interested to hear any
comments on the issue.