|Subject:||Re: [Openexr-devel] Request for feedback: OpenEXR v2.2.1 .so version changes|
|Date:||Fri, 22 Dec 2017 14:30:30 +1300|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0|
Basically, a 2.2.2 release would be in the correct form without the
the questions about whether it is the correct variation. Anyone
looking to grab the latest 2.2.* would get the security fix as a
drop-in replacement for 2.2.0.|
A new 2.2.1 release would be in the correct form, but there is the possibility that the wrong variation as escaped during the window between the first release and the correction. Issue #250 certainly shows that the original 2.2.1 has been picked up.
We would want to deprecate the 2.2.1 releases because of the ambiguity. But, the new official corrected 2.2.1 would still be valid.
I am curious about the reasons why it might be preferable to only doing option a.
As a reminder, we really do want to keep the bumps in version info in the namespace and the SONAME synchronized.
On 12/22/17 12:29, Francois Chardavoine wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|