<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 20.08.2022 um 09:01 schrieb David Fuhrmann <<a href="mailto:david.fuhrmann@gmail.com" class="">david.fuhrmann@gmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear VideoLAN community,<div class=""><br class=""></div><div class="">We would like to do the 3.0.18 release soon, and we would like to try out an improved release process this time:</div><div class=""><br class=""></div><div class="">- First, we will tag 3.0.18-rc and build and publish all release artifacts for testing for the whole community (on <a href="http://download.videolan.org/testing/" class="">download.videolan.org/testing/</a>)</div><div class="">- We will give 1-2 weeks for concentrated testing. Help from everyone is very welcome here, please use the published artifacts to find out whether we have any serious regressions or urgent bugs which need to be fixed before the final release</div><div class="">- The final release will be tagged as 3.0.18</div><div class=""><br class=""></div><div class="">After some discussion with Hugo and j-b, we would like to propose the following timeline:</div><div class=""><br class=""></div><div class="">- 3.0.18-rc tag: Monday August 22nd (next week)</div><div class="">- 3.0.18 tag: Wednesday August 31st (1,5 weeks later)</div><div class=""><br class=""></div><div class="">Would this timeline be fine for everyone who is affected?</div><div class=""><br class=""></div><div class="">I would like to propose a more stringent approach on the timeline for the releases from now on:</div><div class="">In case of some serious issues which might delay the planned dates, I kindly ask to be transparent about it and discuss it here on this mail thread, on this very mailing list. Please always provide a clear and concrete explanation what is blocking the release, including a link to a bug ticket or open merge request which still needs to go in. If we see no veto from anyone, the tag shall happen as planned above.</div><div class=""><br class=""></div><div class="">Thanks for your help.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">David</div></div></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">Hi all,</div><div class=""><br class=""></div><div class="">Thanks to everyone who contributed to the release candidate already. The rc builds are now available on: <a href="https://download.videolan.org/testing/vlc-3.0.18-rc/" class="">https://download.videolan.org/testing/vlc-3.0.18-rc/</a></div><div class="">Any sort of additional testing is very appreciated (also using the release tarballs).</div><div class=""><br class=""></div><div class="">We already found multiple issues, currently blocking the final tag is <a href="https://code.videolan.org/videolan/vlc/-/issues/27276" class="">#27276</a>, and Steves fixes for dvdnav (!2416).</div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">David</div></body></html>