WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
171677
[GTK][WPE] Bump GStreamer version to 1.12 in jhbuild
https://bugs.webkit.org/show_bug.cgi?id=171677
Summary
[GTK][WPE] Bump GStreamer version to 1.12 in jhbuild
Michael Catanzaro
Reported
2017-05-04 11:01:41 PDT
Bump GStreamer version to 1.12 in jhbuild:
https://gstreamer.freedesktop.org/releases/1.12/
We had some pretty bad timing on the 1.10.4 upgrade. ;) It's very important to test with the latest version.
Attachments
Patch
(53.75 KB, patch)
2017-12-12 04:34 PST
,
Carlos Alberto Lopez Perez
no flags
Details
Formatted Diff
Diff
Patch
(53.74 KB, patch)
2017-12-12 04:43 PST
,
Carlos Alberto Lopez Perez
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Carlos Alberto Lopez Perez
Comment 1
2017-05-04 11:30:17 PDT
When doing this, most likely the patch gst-plugins-good-0001-rtpbin-pipeline-gets-an-EOS-when-any-rtpsources-byes.patch has to be recovered back. Check:
https://bugs.webkit.org/show_bug.cgi?id=171595#c13
Carlos Garcia Campos
Comment 2
2017-05-04 23:06:31 PDT
I don't think the idea of the new policy is to always use the latest stable version as soon as it's released. The idea of the policy is to try to test with versions as close as possible to what most of the users will end up using. That's why I proposed to bump versions at the beginning of the cycle to the current stable version, that hopefully would be .1 at the time. In
bug #170500
I proposed versions bumps checking also what distros ship. So, I would wait a bit before using gst 1.12 that was released yesterday. We all know that the actual stable version is not usually .0 but .1 or even .2.
Xabier Rodríguez Calvar
Comment 3
2017-05-05 01:08:04 PDT
(In reply to Carlos Garcia Campos from
comment #2
)
> I don't think the idea of the new policy is to always use the latest stable > version as soon as it's released. The idea of the policy is to try to test > with versions as close as possible to what most of the users will end up > using. That's why I proposed to bump versions at the beginning of the cycle > to the current stable version, that hopefully would be .1 at the time. In >
bug #170500
I proposed versions bumps checking also what distros ship. So, I > would wait a bit before using gst 1.12 that was released yesterday. We all > know that the actual stable version is not usually .0 but .1 or even .2.
Exactly.
Michael Catanzaro
Comment 4
2017-05-05 05:47:40 PDT
(In reply to Carlos Garcia Campos from
comment #2
)
> I don't think the idea of the new policy is to always use the latest stable > version as soon as it's released. The idea of the policy is to try to test > with versions as close as possible to what most of the users will end up > using. That's why I proposed to bump versions at the beginning of the cycle > to the current stable version, that hopefully would be .1 at the time. In >
bug #170500
I proposed versions bumps checking also what distros ship. So, I > would wait a bit before using gst 1.12 that was released yesterday. We all > know that the actual stable version is not usually .0 but .1 or even .2.
I think that usually works, but this time around GStreamer and GNOME release cycles seem to no longer be in sync. We are definitely going to be shipping GStreamer 1.12 to Fedora users next month.
Carlos Garcia Campos
Comment 5
2017-05-05 06:01:04 PDT
(In reply to Michael Catanzaro from
comment #4
)
> (In reply to Carlos Garcia Campos from
comment #2
) > > I don't think the idea of the new policy is to always use the latest stable > > version as soon as it's released. The idea of the policy is to try to test > > with versions as close as possible to what most of the users will end up > > using. That's why I proposed to bump versions at the beginning of the cycle > > to the current stable version, that hopefully would be .1 at the time. In > >
bug #170500
I proposed versions bumps checking also what distros ship. So, I > > would wait a bit before using gst 1.12 that was released yesterday. We all > > know that the actual stable version is not usually .0 but .1 or even .2. > > I think that usually works, but this time around GStreamer and GNOME release > cycles seem to no longer be in sync. We are definitely going to be shipping > GStreamer 1.12 to Fedora users next month.
Are you going to deal with test failures and bugs in WebKit and/or GST?
Michael Catanzaro
Comment 6
2017-05-05 07:39:29 PDT
I can certainly update expectations and file WebKit bugs.
Carlos Garcia Campos
Comment 7
2017-05-05 08:36:52 PDT
(In reply to Michael Catanzaro from
comment #6
)
> I can certainly update expectations and file WebKit bugs.
No, I don't want tests skipped forever, but bugs fixed instead.
Michael Catanzaro
Comment 8
2017-05-05 09:33:12 PDT
Well if you prefer not knowing about bugs affecting our users at all, then sure, let's stick with 1.10.4 for a while....
Carlos Alberto Lopez Perez
Comment 9
2017-09-04 09:17:26 PDT
Is now a good time to bump gstreamer modules to 1.12? Debian testing is now shipping 1.12
Xabier Rodríguez Calvar
Comment 10
2017-09-04 23:54:04 PDT
I don't object.
Carlos Garcia Campos
Comment 11
2017-09-05 00:00:51 PDT
Yes, perfect timing.
Carlos Alberto Lopez Perez
Comment 12
2017-12-12 04:34:30 PST
Created
attachment 329105
[details]
Patch
Carlos Alberto Lopez Perez
Comment 13
2017-12-12 04:43:36 PST
Created
attachment 329107
[details]
Patch Minor cosmetic fix
Carlos Alberto Lopez Perez
Comment 14
2017-12-12 06:58:13 PST
Comment on
attachment 329107
[details]
Patch Clearing flags on attachment: 329107 Committed
r225780
: <
https://trac.webkit.org/changeset/225780
>
Carlos Alberto Lopez Perez
Comment 15
2017-12-12 06:58:19 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug