[jitsi-users] Release versions


#1

How often does the Jitsi project aim to make stable releases of the Jitsi
Meet component projects?

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?

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?

Kind regards,
Rob


#2

Hi there,

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.

Hope that helps.

Cheers,

···

On Jul 2, 2017, at 21:19, Rob <robert.swain@gmail.com> wrote:

--
Saúl


#3

Yes, correct, it is there.

···

On Mon, Jul 3, 2017 at 1:20 AM, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

(Adaptivity is already in stable, is it not Damyan?)


#4

>
> 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?)

Oh, cool!

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?

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?

···

On 3 July 2017 at 08:20, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

> On Jul 2, 2017, at 21:19, Rob <robert.swain@gmail.com> wrote:


#5

>
> 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?)

Oh, cool!

> 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.

Cheers,

···

On Jul 3, 2017, at 10:09, Rob <robert.swain@gmail.com> wrote:
On 3 July 2017 at 08:20, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:
> On Jul 2, 2017, at 21:19, Rob <robert.swain@gmail.com> wrote:

--
Saúl


#6

Still on this topic, is there a way to know which version is currently deployed?

Also, if using the API (https://meet.jit.si/external_api.js) is there a way to control its version? Or, can the API not be compatible with a unstable release?

Best,
Jose

···

On 3 Jul 2017, at 06:57, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

On Jul 3, 2017, at 10:09, Rob <robert.swain@gmail.com> wrote:

On 3 July 2017 at 08:20, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

On Jul 2, 2017, at 21:19, Rob <robert.swain@gmail.com> wrote:

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?)

Oh, cool!

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 <http://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 <http://beta.meet.jit.si/> is deployed automatically though.

Cheers,

--
Saúl

_______________________________________________
users mailing list
users@jitsi.org <mailto:users@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#7

Hi Jose,

Still on this topic, is there a way to know which version is currently deployed?

I don’t think so.

Also, if using the API (https://meet.jit.si/external_api.js) is there a way to control its version? Or, can the API not be compatible with a unstable release?

Not at the moment. You’ll get the latest version, but we do maintain backwards compatibility.

Cheers,

···

On Jul 3, 2017, at 12:30, Jose Simoes <simoes83@gmail.com> wrote:

Best,
Jose

On 3 Jul 2017, at 06:57, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

On Jul 3, 2017, at 10:09, Rob <robert.swain@gmail.com> wrote:

On 3 July 2017 at 08:20, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

On Jul 2, 2017, at 21:19, Rob <robert.swain@gmail.com> wrote:

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?)

Oh, cool!

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.

Cheers,

--
Saúl

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
Saúl


#8

To find jitsi-meet version, check the index.html there is version in
the inclusion of the app.bundle url.
To find lib-jitsi-meet version there is a tag and hash execute in js
console, JitsiMeetJS.version.
To find jvb, jicofo, prosody version, open 2 tabs and in one of them
filter the console with the word version.

Cheers
damencho

···

On Mon, Jul 3, 2017 at 6:04 AM, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

Still on this topic, is there a way to know which version is currently deployed?

I don’t think so.