After the overwhelming feedback about releasing ice4j, there's another
topic: Java 8. It has come up before  and I was strongly against
reasons for this are now gone:
- Debian Stretch has been released
- and Jitsi Desktop 2.10 too
Suggestion: switch to Java 8 after the next Jitsi Meet
Whenever that is, but I assume not far.
The only problem that I am aware of is people with older Debian versions
that already have java7 and jitsi/jitsi-meet installed. Updating only
jitsi-meet in this case would leave a broken system, AFAIK.
I was pointing to this situation in my previous message. From what Jitsi
Meet version could the system be affected if we do not upgrade to Java 8?
Currently all version of jitsi-meet (and its dependencies) work with
java7. I mention the problem because as far as I know it is now the only
thing keeping us from using java8 features in our projects. If and when
we do the switch, it will be announced here on the list.
Yes, please let us know to make sure us to don't upgrade without
installing previously Java 8 in the necesary moment. Although it would
be nice to plan this change so that from a given version, we are all
aware of having previously installed Java 8 before update.
If there is any roadmap to this, it will be good to know it. From what I
read in a previous thread, the idea is to migrate to Java 8 because this
will contribute to the maintainability of the code.
In the scenario where we are using Jessie with Java 7 and Java 8 and
with Jitsi Meet, what changes should we make to instruct Jitsi Meet
components to use Java 8?
Thanks for your reply.
On 15/07/17 18:00, Boris Grozev wrote: