> How often does the Jitsi project aim to make stable releases of the Jitsi Meet component projects?
Every few weeks, but there is no fixed schedule AFAIK.
> Relatedly - there have been a bunch of great improvements recently with the adaptation, jitsi-meet client work and so on - do you have any ETA on the next stable release including this work?
(Adaptivity is already in stable, is it not Damyan?)
> Is jitsi-meet (the web client code) necessarily meant to work with and is tested against the stable jicofo / jitsi-videobridge releases? Or is a specific jitsi-meet version only supposed to work with the same version tags of jicofo / jitsi-videobridge? Or something else?
It depends. Some features need end-to-end changes, so it can only work if everything is on the same page. If you look at the tags of the form “jitsi_meet_XXXX” they are automagically done by Jenkins when the tests pass, and it’s the same tag across the multiple projects.
Sounds good. How extensive are the tests run as part of the Jenkins jobs?
Pretty extensive! https://github.com/jitsi/jitsi-meet-torture
Hope that helps.
It does, thanks!
One more question - what is deployed to meet.jit.si? Is it continuous deployment if the continuous integration run by Jenkins succeeds?
No, we manually deploy when we decide to make a release. Every time tests pass beta.meet.jit.si is deployed automatically though.
On Jul 3, 2017, at 10:09, Rob <email@example.com> wrote:
On 3 July 2017 at 08:20, Saúl Ibarra Corretgé <firstname.lastname@example.org> wrote:
> On Jul 2, 2017, at 21:19, Rob <email@example.com> wrote: