<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Here is my first pass at a policy.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><a href="https://libgeos.org/development/rfcs/rfc11/">https://libgeos.org/development/rfcs/rfc11/</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>If people are agreeable with it, I can put a link to it on the download page -- <a href="https://libgeos.org/usage/download/">https://libgeos.org/usage/download/</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I was also thinking we should put the First Release date on this pages to make it easier to do the math of how old a minor release is.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I think having a Final Release column might be going too far, though other projects do that.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> geos-devel [mailto:geos-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Kurt Schwehr<br><b>Sent:</b> Monday, September 12, 2022 12:23 PM<br><b>To:</b> GEOS Development List <geos-devel@lists.osgeo.org><br><b>Subject:</b> Re: [geos-devel] End of Life Policy (EOL)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Regina,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thank you! This will be a topic of discussion at the NumFocus funded projects later this month where I will be representing GDAL. I will be keeping an eye on the RFC and this thread for aspects that should be discussed at the meeting.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>-kurt<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Mon, Sep 12, 2022 at 9:19 AM Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>That works for me :)<br><br>So I'll draft up an RFC to that effect. So just to be clear, that leaves<br>space open to:<br><br>We may put an update on such a release like 3.4 to the 3.4 branch but we<br>will not bother tagging it.<br><br>I'm not going to say that of course, just saying we are okay with that.<br><br>Thanks,<br>Regina<br><br>> -----Original Message-----<br>> From: geos-devel [mailto:<a href="mailto:geos-devel-bounces@lists.osgeo.org" target="_blank">geos-devel-bounces@lists.osgeo.org</a>] On Behalf Of<br>> Paul Ramsey<br>> Sent: Monday, September 12, 2022 11:37 AM<br>> To: GEOS Development List <<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a>><br>> Subject: Re: [geos-devel] End of Life Policy (EOL)<br>> <br>> As long as the word "support" does not appear in the text. Perhaps "will<br>not<br>> have any further numbered releases" is more correct than "not supported".<br>> <br>> P<br>> <br>> > On Sep 12, 2022, at 8:34 AM, Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>> wrote:<br>> ><br>> > I'm thinking simple fixes and serious security bugs.<br>> ><br>> > I think it's a given we won't break our backs to fix a particular bug<br>> > if it is deemed "De-stabilizing".<br>> > By De-stabilizing, I'm thinking enough code to risk causing a<br>> > particular bigger issue. Pretty much the same policy we have in PostGIS<br>> no?<br>> ><br>> > But by saying EOL we are saying we will absolutely NEVER push fixes to<br>it.<br>> ><br>> > If some corporate paying customer is running something as crazy as<br>> > 3.4, you should just fork that for them and patch it there and deal<br>> > with their upgrade issues some other day.<br>> ><br>> > Thanks,<br>> > Regina<br>> ><br>> ><br>> ><br>> ><br>> >> -----Original Message-----<br>> >> From: geos-devel [mailto:<a href="mailto:geos-devel-bounces@lists.osgeo.org" target="_blank">geos-devel-bounces@lists.osgeo.org</a>] On<br>> >> Behalf Of Paul Ramsey<br>> >> Sent: Monday, September 12, 2022 11:20 AM<br>> >> To: GEOS Development List <<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a>><br>> >> Subject: Re: [geos-devel] End of Life Policy (EOL)<br>> >><br>> >><br>> >><br>> >>> On Sep 12, 2022, at 8:12 AM, Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>> wrote:<br>> >>><br>> >>> I'd like to make an RFC proposing a standardish End of Like Policy<br>> >>><br>> >>> Does anyone have an issue with that?<br>> >><br>> >> Only insofar as there's this idea that we support any particular<br>> >> version<br>> > at all.<br>> >> Honestly, there are some bugs I just cannot be bothered to try and<br>> >> fix (anything overlay pre 3.9, right? the fix there is to upgrade)<br>> >> but at the<br>> > same<br>> >> time, I don't really mind pulling back trivial stuff pretty far. What<br>> >> does<br>> > it mean<br>> >> to "support" this stuff anyways? Comes right down to it, if a paying<br>> > customer<br>> >> on 3.4 has an issue and is unable to upgrade, we'll break our fingers<br>> >> to<br>> > try and<br>> >> fix it. But that has to do with our corporate support, not some<br>> >> community commitment to support.<br>> >><br>> >> ???<br>> >><br>> >> P<br>> >><br>> >><br>> >>><br>> >>> I'm thinking of a policy along the lines of<br>> >>><br>> >>> We support a release generally at most X plus years after the first<br>> >>> version of it, but we have discretion to increase that if needed.<br>> >>><br>> >>> X = 3 - 5 feels about right.<br>> >>><br>> >>> How do people feel about that?<br>> >>><br>> >>> If so I can draft up an RFC about that and we can edit if we are<br>> >>> comfortable with that and start EOL'ing other releases besides the<br>> >>> 3.5 I<br>> >> recently EOL'd.<br>> >>><br>> >>> Thanks,<br>> >>> Regina<br>> >>><br>> >>> _______________________________________________<br>> >>> geos-devel mailing list<br>> >>> <a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>> >>> <a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><br>> >><br>> >> _______________________________________________<br>> >> geos-devel mailing list<br>> >> <a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>> >> <a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><br>> ><br>> > _______________________________________________<br>> > geos-devel mailing list<br>> > <a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>> > <a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><br>> <br>> _______________________________________________<br>> geos-devel mailing list<br>> <a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>> <a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><br><br>_______________________________________________<br>geos-devel mailing list<br><a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><o:p></o:p></p></blockquote></div></div></div></body></html>