<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 1, 2019 at 7:04 PM Mario *LigH* Rohkrämer <<a href="mailto:contact@ligh.de">contact@ligh.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Aruna Matheswaran schrieb am 01.08.2019 um 15:21:<br>
> <br>
> <br>
> On Wed, Jul 31, 2019 at 7:21 PM Mario *LigH* Rohkrämer <<a href="mailto:contact@ligh.de" target="_blank">contact@ligh.de</a> <br>
> <mailto:<a href="mailto:contact@ligh.de" target="_blank">contact@ligh.de</a>>> wrote:<br>
> <br>
> Aruna Matheswaran schrieb am 31.07.2019 um 07:52:<br>
> > Hi all,<br>
> ><br>
> > Version 3.1.2 of x265 is released with the fix for issue #498<br>
> ><br>
> <<a href="https://bitbucket.org/multicoreware/x265/issues/498/31rc-library-hangs-during-encoder_close" rel="noreferrer" target="_blank">https://bitbucket.org/multicoreware/x265/issues/498/31rc-library-hangs-during-encoder_close</a>>.<br>
> <br>
> > Check out our downloads page<br>
> > <<a href="https://bitbucket.org/multicoreware/x265/downloads/" rel="noreferrer" target="_blank">https://bitbucket.org/multicoreware/x265/downloads/</a>>for the tarball.<br>
> ><br>
> > Looking forward to your feedback.<br>
> > --<br>
> > Regards,<br>
> > Aruna<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > x265-devel mailing list<br>
> > <a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a> <mailto:<a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a>><br>
> > <a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
> <br>
> I might be wrong, but ... tagging without merging may result in two<br>
> parallel branches: "default" with the code and "release" with the tags.<br>
> And if you are unlucky (like right now), the "tip" points to the newest<br>
> tag with outdated code.<br>
> <br>
> <br>
> Mario, We have implemented a new release process in v3.1. The plan is to <br>
> maintain a separate branch for every release of x265. All the bug fixes <br>
> specific to release "X.X" will be pushed to "Release_X.X" with a tag <br>
> "X.X.X" and the fix will be grafted to all the succeeding release <br>
> branches as well into default. This way the integrating application will <br>
> have the freedom to pick whichever version of x265 it wants as all the <br>
> bug fixes specific to that version will be available in the release <br>
> branch unlike earlier where all the bug fixes go into the tip of stable <br>
> and the user is forced to use the recent release of x265.<br>
> <br>
> Stable will get periodic merges from default and once an ample amount of <br>
> work goes into stable we'll create a new release branch and tag the new <br>
> version.<br>
> <br>
> <br>
> -- <br>
> <br>
> Fun and success!<br>
> <br>
> Mario *LigH* Rohkrämer<br>
> <a href="mailto:maito%3Acontact@ligh.de" target="_blank">maito:contact@ligh.de</a> <mailto:<a href="mailto:maito%253Acontact@ligh.de" target="_blank">maito%3Acontact@ligh.de</a>><br>
> _______________________________________________<br>
> x265-devel mailing list<br>
> <a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a> <mailto:<a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a>><br>
> <a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
> <br>
> <br>
> <br>
> -- <br>
> Regards,<br>
> Aruna<br>
> <br>
> <br>
> _______________________________________________<br>
> x265-devel mailing list<br>
> <a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a><br>
> <a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
<br>
<br>
Thank you, Aruna. This way you will keep track of bugfixes.<br>
<br>
But it seems to me that the development of new features in the "default" <br>
branch will not be available in releases until you explicitly merge <br>
them. So testers will have either "unfixed" builds with new features or <br>
fixed builds with old features only ... until the fixed "release" branch <br>
may be merged with the experimental "default" branch once in a while.<br></blockquote><div><br></div><div>As soon as we push a fix into release branch, we graft the same into default. So, you should be getting new features with fixes in default.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-- <br>
<br>
Fun and success!<br>
<br>
Mario *LigH* Rohkrämer<br>
<a href="mailto:maito%3Acontact@ligh.de" target="_blank">maito:contact@ligh.de</a><br>
_______________________________________________<br>
x265-devel mailing list<br>
<a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><font face="georgia, serif">Regards,</font><div><font face="georgia, serif">Aruna</font></div></div></div></div>