[jitsi-dev] New updates for testing repo


#1

Hi Jitsi team!

It's been a while since I've seen updates in testing repo. I think that
so far this year I have not seen any (although I may also be wrong). Is
it possible or maybe there is a problem with the package generation process?

These are the latest versions that I can find in the repo:

jitsi-meet: 1.0.2718-1
jitsi-meet-prosody: 1.0.2516-1
jitsi-meet-web: 1.0.2516-1
jitsi-meet-web-config: 1.0.2516-1
jitsi-videobridge: 1018-1
jicofo: 1.0-392-1

Thanks in advance.

Kind regards,
Daniel


#2

I may be wrong, but I think "stable" and "unstable" are the ones that
get updates:

https://download.jitsi.org/stable/
https://download.jitsi.org/unstable/

"Unstable" getting all the builds and "stable" -- well, the stable
ones. :slight_smile: Maybe there is no room (need, time etc.) for "testing", but
I'm not from the team, I may be wrong.

BTW I'm using "stable" and "unstable" for production and dev platforms
respectively and it's all been OK, but YMMV.

···

On Tue, 20 Feb 2018 15:35:15 -0300 Daniel Bareiro wrote:

Hi Jitsi team!

It's been a while since I've seen updates in testing repo. I think that
so far this year I have not seen any (although I may also be wrong). Is
it possible or maybe there is a problem with the package generation
process?

These are the latest versions that I can find in the repo:

jitsi-meet: 1.0.2718-1
jitsi-meet-prosody: 1.0.2516-1
jitsi-meet-web: 1.0.2516-1
jitsi-meet-web-config: 1.0.2516-1
jitsi-videobridge: 1018-1
jicofo: 1.0-392-1

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#3

Hi. Yasen.

Hi Jitsi team!

It's been a while since I've seen updates in testing repo. I think that
so far this year I have not seen any (although I may also be wrong). Is
it possible or maybe there is a problem with the package generation
process?

These are the latest versions that I can find in the repo:

jitsi-meet: 1.0.2718-1
jitsi-meet-prosody: 1.0.2516-1
jitsi-meet-web: 1.0.2516-1
jitsi-meet-web-config: 1.0.2516-1
jitsi-videobridge: 1018-1
jicofo: 1.0-392-1

I may be wrong, but I think "stable" and "unstable" are the ones that
get updates:

https://download.jitsi.org/stable/
https://download.jitsi.org/unstable/

"Unstable" getting all the builds and "stable" -- well, the stable
ones. :slight_smile: Maybe there is no room (need, time etc.) for "testing", but
I'm not from the team, I may be wrong.

BTW I'm using "stable" and "unstable" for production and dev platforms
respectively and it's all been OK, but YMMV.

Boris Grozev, from a conversation he had some time ago with Damian
Minkov, told me that packets that pass a set of automatic tests go to
the Testing repository, whereas Stable is only manually updated.

That's why I found it strange to not see updates in all this time. At
least I do not remember seeing them.

What versions are you currently running from the Unstable repo?

Thanks for your reply.

Kind regards,
Daniel

···

On 20/02/18 15:43, Yasen Pramatarov wrote:


#4

I see what you mean. I don't know the status of "testing".

Currently jitsi-meet 2807, videobridge 1031 and all the others from
"unstable" are running here: https://demo.lindeas.com/ while the
"stable" ones are on https://meet.lindeas.com/

We didn't have issues with these, but like I said they are development
and/or demonstration servers, they don't get a lot of beating, for the
clients we use "stable" repo.

I may be wrong, but I think all the packages (including "unstable")
have to pass automated tests before being uploaded. But I'm already
guessing here.

The point is that "unstable" works pretty well for pre-production, debs
are installable and are OK as packages (while "stable" should have
gotten more bugfixing of the code itself).

I'm not a jitsi dev, just speaking as a user.

···

On Tue, 20 Feb 2018 18:33:48 -0300 Daniel Bareiro wrote:

Hi. Yasen.

On 20/02/18 15:43, Yasen Pramatarov wrote:

Hi Jitsi team!

It's been a while since I've seen updates in testing repo. I think
that so far this year I have not seen any (although I may also be
wrong). Is it possible or maybe there is a problem with the package
generation process?

These are the latest versions that I can find in the repo:

jitsi-meet: 1.0.2718-1
jitsi-meet-prosody: 1.0.2516-1
jitsi-meet-web: 1.0.2516-1
jitsi-meet-web-config: 1.0.2516-1
jitsi-videobridge: 1018-1
jicofo: 1.0-392-1

I may be wrong, but I think "stable" and "unstable" are the ones
that get updates:

https://download.jitsi.org/stable/
https://download.jitsi.org/unstable/

"Unstable" getting all the builds and "stable" -- well, the stable
ones. :slight_smile: Maybe there is no room (need, time etc.) for "testing", but
I'm not from the team, I may be wrong.

BTW I'm using "stable" and "unstable" for production and dev
platforms respectively and it's all been OK, but YMMV.

Boris Grozev, from a conversation he had some time ago with Damian
Minkov, told me that packets that pass a set of automatic tests go to
the Testing repository, whereas Stable is only manually updated.

That's why I found it strange to not see updates in all this time. At
least I do not remember seeing them.

What versions are you currently running from the Unstable repo?

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#5

Hi,

We have a build pipeline and after testing succeeds for the unstable
packages a bunch of other tests we run and when that one succeeds
packages are automatically moved to testing. But recently we started
modifying the jitsi-meet-torture for adding and some mobile testing
which broke that pipeline and we will be fixing that in the next few
weeks. That is the reason that testing repo was not updated for a
while. Sorry about that.
As Yasen pointed unstable should be fine, and as it happened the
previous few weeks we moved packages from unstable to stable to match
our deployment.

Regards
damencho

···

On Wed, Feb 21, 2018 at 12:56 PM, Yasen Pramatarov <yasen@lindeas.com> wrote:

On Tue, 20 Feb 2018 18:33:48 -0300 Daniel Bareiro wrote:

Hi. Yasen.

On 20/02/18 15:43, Yasen Pramatarov wrote:

Hi Jitsi team!

It's been a while since I've seen updates in testing repo. I think
that so far this year I have not seen any (although I may also be
wrong). Is it possible or maybe there is a problem with the package
generation process?

These are the latest versions that I can find in the repo:

jitsi-meet: 1.0.2718-1
jitsi-meet-prosody: 1.0.2516-1
jitsi-meet-web: 1.0.2516-1
jitsi-meet-web-config: 1.0.2516-1
jitsi-videobridge: 1018-1
jicofo: 1.0-392-1

I may be wrong, but I think "stable" and "unstable" are the ones
that get updates:

https://download.jitsi.org/stable/
https://download.jitsi.org/unstable/

"Unstable" getting all the builds and "stable" -- well, the stable
ones. :slight_smile: Maybe there is no room (need, time etc.) for "testing", but
I'm not from the team, I may be wrong.

BTW I'm using "stable" and "unstable" for production and dev
platforms respectively and it's all been OK, but YMMV.

Boris Grozev, from a conversation he had some time ago with Damian
Minkov, told me that packets that pass a set of automatic tests go to
the Testing repository, whereas Stable is only manually updated.

That's why I found it strange to not see updates in all this time. At
least I do not remember seeing them.

What versions are you currently running from the Unstable repo?

I see what you mean. I don't know the status of "testing".

Currently jitsi-meet 2807, videobridge 1031 and all the others from
"unstable" are running here: https://demo.lindeas.com/ while the
"stable" ones are on https://meet.lindeas.com/

We didn't have issues with these, but like I said they are development
and/or demonstration servers, they don't get a lot of beating, for the
clients we use "stable" repo.

I may be wrong, but I think all the packages (including "unstable")
have to pass automated tests before being uploaded. But I'm already
guessing here.

The point is that "unstable" works pretty well for pre-production, debs
are installable and are OK as packages (while "stable" should have
gotten more bugfixing of the code itself).

I'm not a jitsi dev, just speaking as a user.

--
> Yasen Pramatarov
> Lindeas Ltd. https://lindeas.com
> 'working on GNU/Linux ideas'
> Professional Jitsi Meet services

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