The corresponding relationship between jitsi DEB version and GitHub tag

#1

example

dpkg -l | grep jicofo

ii  jicofo                                 1.0-644-1                                       all          JItsi Meet COnference FOcus

Is the relationship between versions

Version 1.0

644==github tag name

What do you mean by - 1?

Am I right to understand that?

#2

(no jitsi dev here)
it’s managed here so the -1 can’t be anything else (unless someone creates a build-new-package-2.sh to change the -1 to -2 if at some point there is a build problem maybe ?)

#3

Thank you for your reply. I just want to know if 644 corresponds to GitHub tag name

#4

yes, that’s it. see resources/build_deb_package.sh for jicofo. I think that BUILD_NUMBER environment variable (the tag) is set by whatever tool Jitsi devs are using to build Jicofo (Jenkins or whatever).

#5

Yep, https://github.com/jitsi/jicofo/releases/tag/644

#6

Thank you very much for your reply. Can you help me answer this question?

#7

I executed dpkg -l | grep jitsi

ii  jitsi-meet                             2.0.5142-1                                      all          WebRTC JavaScript video conferences
ii  jitsi-meet-prosody                     1.0.4466-1                                      all          Prosody configuration for Jitsi Meet
ii  jitsi-meet-turnserver                  1.0.4466-1                                      all          Configures coturn to be used with Jitsi Meet
ii  jitsi-meet-web                         1.0.4466-1                                      all          WebRTC JavaScript video conferences
ii  jitsi-meet-web-config                  1.0.4466-1                                      all          Configuration for web serving of Jitsi Meet
ii  jitsi-videobridge2                     2.1-376-g9f12bfe2-1                             all          WebRTC compatible Selective Forwarding Unit (SFU)

The tag on GitHub corresponding to jvb is 376

The final submission was six years ago. Is this correct?

#8

No, that is not correct. Here you see the old and the new version scheme. And we have not managed to transition to the new scheme for two years now.
The version 2.1-376-g9f12bfe2-1 is what we hope to have at some point on all components, except on jitsi-meet the meta package that binds all together. This version is ${MAJOR}.${MINOR}-${NUMBER_OF_COMMITS_SINCE_LATEST_MAJOR_OR_MINOR_BUMP}-g${GIT_COMMIT_HASH}. So you can see the version itself points to the source code directly and there is no tag for that version.

#9

I understand that the DEB of jvb does not have a corresponding GitHub tag, and needs to use the latest master code. If so, the master is updated frequently, which is not a very stable branch

#10

That is not true. I was showing you that every debian version has a corresponding hash that serves the same way as a tag - it is a point in the code from which this binary was produced. The only difference is that the tag has a name, but also the tag is from the master branch of the repo.

#11

that’s too bad. I can’t find the corresponding commit of 2.1-376-g9f12bfe2-1. Will there be plans to consider issuing DEB and tag GitHub?

#12

As I said earlier this is already the case.

It is easy as:

git clone https://github.com/jitsi/jitsi-videobridge.git
git checkout 9f12bfe2
#13

Thank you. I’ve seen it
Can you help me answer this question?

https://community.jitsi.org/t/working-modes-of-multiple-jvb/88532/7

Thank you. I’ve seen it
Can you help me answer this question?
I want to know what is the working mode of multiple jvb? Is it effective for him to increase the maximum number of people in the meeting?