WebRTC release notes not being published

[antozo...@gmail.com]

Hi guys,

Earlier we used have webRTC release notes being published for every chrome version but its been stopped few versions back.

I know its a lot work to gather the resources and publish the release notes, but it was very useful as a developer focused on webRTC. The release notes that gets published with chrome is not very detailed and highlights only the major changes. We used to get even minor changes and issue fixes and upcoming PSA and deprecation announcement.

Kindly consider resuming WebRTC release notes publishing

Thanks in advance

~Anto

[Matt Knowles]

I second that but in the mean time, I have been walking the change sets from the link below.
Not exactly the same as the very well prepared release notes posted here but at least you get an idea of what has changed.

The WebRTC column is in the middle. 
https://chromiumdash.appspot.com/branches

Matt

[Chao Liu]

It's not the first time Google stopped publishing the release notes.

The last time it seemed the previous guy left the team. A different name started to publish the release notes after a while.

I am not sure whether we should worry about that Google may stop maintaining WebRTC at some point.

Hope not since it's part of HTML5 and Chrome. But it's Google...

[Harald Alvestrand]

The last bunch of release notes were prepared by Philipp Hancke, who is now at Meta (previously at Microsoft). I did the actual posting to the mailing list.

As mentioned, it is a bit of work to prepare these, and we haven't seen that much active feedback on them from developers. Nice to hear that someone found them a benefit.

It's been one of those "it's nobody's real job, so volunteers did it" tasks that tends to eventually peter out.

Harald

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/5e32ac30-4924-436b-8c67-4026235dce72n%40googlegroups.com.

[Vitaly Ivanov]

I think release notes were really useful to get an overview of the latest developments. I didn't realize though that some sort of feedback was required - surely it'd get lotsa thumb-ups if it was Facebook or LinkedIn, but in an email group it would turn rather spammy

To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/CAOqqYVGeH6L%3DvPVyzynkxKOkp3fvtFJHhK2j3hMtPzHVuNv3hQ%40mail.gmail.com.

[philipp.hancke]

Am Di., 25. März 2025 um 01:38 Uhr schrieb Vitaly Ivanov <witaly...@gmail.com>:

I think release notes were really useful to get an overview of the latest developments.

Thing is the release notes covered somewhere between a third and half the commits because a lot of commits land with either the "None" issue or are associated to issues that are kept open forever (the H26x packet buffer is a good example and as we have seen it did cause regressions)

the sad reality is that the monorail migration broke the little script I had crawling the issue tracker.

To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/CAFa3_%3D9Hra%3D1SFRieNb%3DeebjuvTHqC2nGX8ixE7xx%3DBuukW5yA%40mail.gmail.com.

[Chao Liu]

Harald and Philipp,

Thanks for your replies. I understand the challenges to keep it going and appreciate your efforts.

From a WebRTC user's respective, it's critical that the dev team could provide updates periodically. The release notes are the natural way to do it.

There are two aspects of this:

- We would like to know new features that're coming to coordinate our work accordingly.

  Monitoring forum posts / bugs is just too much work. Most users cannot afford it.

- Knowing that the dev team is fixing bugs and improve things, even if it's not directly related to a user's use case, is a sign that this project is still well maintained.

  As a user, the worst scenario is that Google doesn't care about it anymore. Unfortunately, this is nothing unusual for Google products / projects.

[Sean DuBois]

If you want summaries https://bloggeek.me/webrtc-insights/ is the best option.

As a developer it is hard to know what people know (or don't know). You also don’t get feedback

if the release notes are good or not.

To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/dedc5138-7f63-44e3-a200-bc49bec4a503n%40googlegroups.com.

[Tsahi Levent-Levi]

Chao,

We'd all love if this project will be treated at a higher priority inside Google and for the good of the whole world.

Alas, Google isn't doing it out of the goodness of their hearts, but rather due to their own internal needs. And when they can, they help "the rest of us".

Here's something I wrote almost exactly 2 years ago and is still valid today: https://bloggeek.me/webrtc-google-outsourcing/

While at it, I hope you filled out the survey - it is about understanding what the developers out there use WebRTC for --> https://near-hollyhock-921.notion.site/1b6eb21754f68054a600de1cb79ce194?pvs=105

Regards,

Tsahi

To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/dedc5138-7f63-44e3-a200-bc49bec4a503n%40googlegroups.com.

--

Regards,

Tsahi Levent-Levi

Analyst & Consultant

BlogGeek.me

Check out my latest free eBook: Top 7 WebRTC Video Quality Metrics and KPIs