<div dir="auto"><div>>Also, it was suggested that we (cinelerra-gg) can create different git branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready.</div><div dir="auto"><br></div><div dir="auto">+1 for testing branch. </div><div dir="auto"><br></div><div>Best regards,</div><div dir="auto">Andrey</div><div data-smartmail="gmail_signature"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пн, 20 мая 2024 г., 21:50 Andrew Randrianasulu via Cin <<a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">News item at <a href="http://linux.org.ru" target="_blank" rel="noreferrer">linux.org.ru</a> - because official one just few lines without any picture :)<div dir="auto"><br></div><div dir="auto"><a href="https://www.linux.org.ru/news/multimedia/17621213" target="_blank" rel="noreferrer">https://www.linux.org.ru/news/multimedia/17621213</a><br></div><div dir="auto"><br></div><div dir="auto">Also, it was suggested that we (cinelerra-gg) can create different git branch < named, say, "testing" > for "potentially unstable" patches, like current ffmpeg 7.0 patchset and then merge back to main/stable when feature is deemed ready. So, "main" releases will be once in half year, year but they will look more like releases, with Changelog looking less like git log :)</div></div>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" target="_blank" rel="noreferrer">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div>