Re: Python bindings: aliasing gdal.Open and gdal.OpenEx

--===============7606956802576206453==
Content-Type: multipart/alternative; boundary="0000000000009c23c206549bafdd"

--0000000000009c23c206549bafdd
Content-Type: text/plain; charset="UTF-8"

Hi Even,


> So we're
> more in a situation where we land a few backwards incompatible change
> each (non bugfix) release.
>

A possible mitigation is to use a release model where we backport certain
fixes to an LTS release, allowing users who don't need the
latest-and-greatest to deal with breaking changes every N years, rather
than every 6 months. Obviously that would come at a significant cost to the
project, not a decision to be taken lightly.

Dan

--0000000000009c23c206549bafdd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><div>Hi E=
ven,</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-le=
ft-color:rgb(204,204,204);padding-left:1ex">So we&#39;re <br>
more in a situation where we land a few backwards incompatible change <br>
each (non bugfix) release.<br></blockquote><div><br></div><div>A possible m=
itigation is to use a release model where we backport certain fixes to an L=
TS release, allowing users who don&#39;t need the latest-and-greatest to de=
al with breaking changes every N years, rather than every 6 months. Obvious=
ly that would come at a significant cost to the project, not a decision to =
be taken lightly.</div><div><br></div><div>Dan</div></div></div>

--0000000000009c23c206549bafdd--

--===============7606956802576206453==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev

--===============7606956802576206453==--