Re: Request for feedback: OpenEXR v2.2.1 .so version changes
Francois Chardavoine <[email protected]> Thu, 21 Dec 2017 15:29:08 -0800
| Newsgroups | gmane.comp.video.openexr.devel |
|---|---|
| Message-ID | <CADBZUEgUf6m5JJT2Yhp5eUd6QGDW0K8NOe60e3aGidP-7EnyBg@mail.gmail.com> |
--===============8481548449786857913== Content-Type: multipart/alternative; boundary="94eb2c1259064330540560e21221" --94eb2c1259064330540560e21221 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Why do b) as well if we go with a) ? On Thu, Dec 21, 2017 at 1:52 PM, Richard Addison-Wood <[email protected]= > wrote: > How about both options a and b? > > > On 12/22/17 05:56, Wayne Wooten wrote: > > > > The Pixar team would prefer option A as well. > > =E2=80=94Wayne > > On December 21, 2017 at 8:48:15 AM, Larry Gritz ([email protected]) wrote= : > > I don't have a strong opinion, but the widely used convention is that you > should bump the so version when link compatibility changes. I'm ok with > (a), I don't think I've yet seen 2.2.1 in the wild. > > > On Dec 20, 2017, at 11:31 PM, Francois Chardavoine <[email protected]= m> > wrote: > > It has been brought to our attention that the decision to increment the s= o > version as part of the 2.2.1 release may be problematic: > https://github.com/openexr/openexr/issues/250 > > It would be great to get any additional community commentary on this. The > .so version was bumped up mainly as an (admittedly conservative) > precautionary measure, since it had been a long time since the previous > release. Given that these are security vulnerability fixes, it's > understandable that there might be in some cases a desire to be able to > drop in replacement builds of OpenEXR without recompiling the host > application. > > Two options we can take are: > > - a)- patch the currently tagged 2.2.1 to no longer include an .so > version change. This could be controversial unless we get feedback tha= t no > one has adopted 2.2.1 in any significant way yet (to avoid confusion a= round > "what version of 2.2.1 did you use?") > - b)- release a 2.2.2 version which is identical to 2.2.1, except with > the older so version. This is somewhat inelegant, but likely cleaner t= han > option a). > > > Does the community have any strong positions on this either way? > Francois. > > > -- > Larry Gritz > [email protected] > > > > > _______________________________________________ > Openexr-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/openexr-devel > > > > _______________________________________________ > Openexr-devel mailing [email protected]://lists.nongnu.or= g/mailman/listinfo/openexr-devel > > > > _______________________________________________ > Openexr-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/openexr-devel > > --94eb2c1259064330540560e21221 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Why do b) as well if we go with a) ?<div><br><div class=3D= "gmail_extra"><br><div class=3D"gmail_quote">On Thu, Dec 21, 2017 at 1:52 P= M, Richard Addison-Wood <span dir=3D"ltr"><<a href=3D"mailto:richard@wet= afx.co.nz" target=3D"_blank">[email protected]</a>></span> wrote:<br>= <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> =20 =20 =20 <div text=3D"#000000" bgcolor=3D"#FFFFFF"> How about both options a and b?<div><div class=3D"h5"><br> <br> <div class=3D"m_-3727155238712743362moz-cite-prefix">On 12/22/17 05:56,= Wayne Wooten wrote:<br> </div> <blockquote type=3D"cite"> =20 =20 <div id=3D"m_-3727155238712743362bloop_customfont" style=3D"font-fami= ly:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-hei= ght:auto"><br> </div> =C2=A0 <div>=C2=A0The Pixar team would prefer option A as well.</div> <div>=C2=A0</div> <div>=C2=A0 =E2=80=94Wayne<br> <br> <p class=3D"m_-3727155238712743362airmail_on">On December 21, 2017 = at 8:48:15 AM, Larry Gritz (<a href=3D"mailto:[email protected]" target=3D"_blank">lg@= larrygritz.com</a>) wrote:</p> <blockquote type=3D"cite" class=3D"m_-3727155238712743362clean_bq">= <span> <div style=3D"word-wrap:break-word"> <div> =20 I don't have a strong opinion, but the widely used convention is that you should bump the so version when link compatibility changes. I'm ok with (a), I don't think I've ye= t seen 2.2.1 in the wild. <div><br> <div><br> <div> <blockquote type=3D"cite"> <div>On Dec 20, 2017, at 11:31 PM, Francois Chardavoine <<a href=3D"mailto:[email protected]" tar= get=3D"_blank">[email protected]</a>> wrote:</div> <br class=3D"m_-3727155238712743362Apple-interchang= e-newline"> <div> <div dir=3D"ltr"> <div>It has been brought to our attention that the decision to increment the so version as part of the 2.2.1 release may be problematic:</div> <div><a href=3D"https://github.com/openexr/open= exr/issues/250" target=3D"_blank">https://github.com/openexr/<wbr>openexr/i= ssues/250</a><br> </div> <div><br> </div> It would be great to get any additional community commentary on this. The .so version was bumped up mainly as an (admittedly conservative) precautionary measure, since it had been a long time since the previous release. Given that these are security vulnerability fixes, it's understandable that there might be in some cases a desire to be able to drop in replacement builds of OpenEXR without recompiling the host application. <div><br> </div> <div>Two options we can take are:</div> <div> <ul> <li>a)- patch the currently tagged 2.2.1 to no longer include an .so version change. This could be controversial unless we get feedback that no one has adopted 2.2.1 in any significant way yet (to avoid confusion around "what version of 2.2.1 did you use?")<br> </li> <li>b)- release a 2.2.2 version which is identical to 2.2.1, except with the older so version. This is somewhat inelegant, but likely cleaner than option a).<br> </li> </ul> </div> <div><br> </div> <div>Does the community have any strong positions on this either way?</div> <div>Francois.</div> </div> </div> </blockquote> </div> <br> <div> <div style=3D"word-wrap:break-word"> <div style=3D"color:rgb(0,0,0);font-family:Helvetic= a;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:nor= mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n= one;white-space:normal;word-spacing:0px">--</div> <div style=3D"color:rgb(0,0,0);font-family:Helvetic= a;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:nor= mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n= one;white-space:normal;word-spacing:0px">Larry Gritz</div> <div style=3D"color:rgb(0,0,0);font-family:Helvetic= a;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:nor= mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n= one;white-space:normal;word-spacing:0px"><a href=3D"mailto:[email protected]= m" target=3D"_blank">[email protected]</a></div> <div style=3D"color:rgb(0,0,0);font-family:Helvetic= a;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:nor= mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n= one;white-space:normal;word-spacing:0px"><br> </div> <br class=3D"m_-3727155238712743362Apple-interchang= e-newline"> </div> <br class=3D"m_-3727155238712743362Apple-interchange-= newline"> </div> <br> </div> </div> ______________________________<wbr>_________________ <br> Openexr-devel mailing list <br> <a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a> <br> <a href=3D"https://lists.nongnu.org/mailman/listinfo/openex= r-devel" target=3D"_blank">https://lists.nongnu.org/<wbr>mailman/listinfo/o= penexr-devel</a> <br> </div> </div> </span></blockquote> </div> <br> <fieldset class=3D"m_-3727155238712743362mimeAttachmentHeader"></fiel= dset> <br> <pre>______________________________<wbr>_________________ Openexr-devel mailing list <a class=3D"m_-3727155238712743362moz-txt-link-abbreviated" href=3D"mailto:= [email protected]" target=3D"_blank">[email protected]</a> <a class=3D"m_-3727155238712743362moz-txt-link-freetext" href=3D"https://li= sts.nongnu.org/mailman/listinfo/openexr-devel" target=3D"_blank">https://li= sts.nongnu.org/<wbr>mailman/listinfo/openexr-devel</a> </pre> </blockquote> <br> </div></div></div> <br>______________________________<wbr>_________________<br> Openexr-devel mailing list<br> <a href=3D"mailto:[email protected]">[email protected]</a><br= > <a href=3D"https://lists.nongnu.org/mailman/listinfo/openexr-devel" rel=3D"= noreferrer" target=3D"_blank">https://lists.nongnu.org/<wbr>mailman/listinf= o/openexr-devel</a><br> <br></blockquote></div><br></div></div></div> --94eb2c1259064330540560e21221-- --===============8481548449786857913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Openexr-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/openexr-devel --===============8481548449786857913==--