<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'>No. Not for beta. <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'>For release time we should take care of the blockers and do what we can with the other more serious ones. Others we'd just push to the next milestone.<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'>That said I'm not seeing that many blockers and some of them are questionable blockers (just dismissed one in fact) or are issues in PostgreSQL / GEOS / GDAL so out of our control.<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://trac.osgeo.org/postgis/query?priority=blocker&status=assigned&status=new&status=reopened">https://trac.osgeo.org/postgis/query?priority=blocker&status=assigned&status=new&status=reopened</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'><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 style='margin-left:.5in'><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'> postgis-devel [mailto:postgis-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Daniel Baston<br><b>Sent:</b> Wednesday, August 31, 2016 8:33 AM<br><b>To:</b> PostGIS Development Discussion <postgis-devel@lists.osgeo.org><br><b>Subject:</b> Re: [postgis-devel] Vote to call PostGIS 2.3 beta1 next week<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>Hi Regina,<o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>There are over 20 defects assigned to each of the 2.1.9, 2.2.3, and 2.3.0 milestones, with at least one "blocker" in each. Would these tickets need to be resolved before proceeding with a release?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Dan<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>On Tue, Aug 30, 2016 at 4:27 PM, Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>> wrote:<o:p></o:p></p><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 style='margin-left:.5in'>I'd like to release a PostGIS 2.3 beta1 next week. I think all major<br>milestones I noted since<br><br><a href="https://lists.osgeo.org/pipermail/postgis-devel/2016-July/025872.html" target="_blank">https://lists.osgeo.org/pipermail/postgis-devel/2016-July/025872.html</a><br><br>have been committed.<br><br>Namely,<br><br>1) BRIN support in place<br>2) schema qualifying all our calls and making PostGIS not relocateable<br>3) Tiger 2016 upgrade<br>4) ST_Segmentize for geography fixed.<br><br>The other things we discussed, which are still not committed are the<br>following:<br>These I feel should be just pushed to 2.4 because they are<br>a) Too far from done or b) currently are in conflict with our code base<br>c) Too small of a feature to risk missing PostgreSQL 9.6 release.<br><br>5) I still have some testing to do with parallelizing but just assume I do<br>that when we release beta<br><br>-- there will probably be one more commit for address_standardizer for<br>PostGIS 2.2 and PostGIS 2.3, but that should be done before end this week<br><br>One which I didn't mention is this -<br><a href="https://trac.osgeo.org/postgis/ticket/3528" target="_blank">https://trac.osgeo.org/postgis/ticket/3528</a> (Use tree-based distance<br>calculation by default in geography )<br>(Paul Ramsey are you going to have time to look at this before now and next<br>week (to risky you think to do now) or should we just push to 2.4?)<br><br><br>Everything else on plate are bug fixes that we should have mostly fixed by<br>release time.<br><br>-- New features that I'm planning to punt to 2.4<br>6) Precision Model support - Dan doesn't have time and lots of lossedns<br>7) ST_Angle function - <a href="https://github.com/postgis/postgis/pull/97" target="_blank">https://github.com/postgis/postgis/pull/97</a><br>8) Validity Flag - <a href="https://github.com/postgis/postgis/pull/99" target="_blank">https://github.com/postgis/postgis/pull/99</a><br>9) ST_AsText -- adding optional precision argument --<br><a href="https://github.com/postgis/postgis/pull/94" target="_blank">https://github.com/postgis/postgis/pull/94</a><br>10) ST_AsGeoBuf -- <a href="https://github.com/postgis/postgis/pull/108" target="_blank">https://github.com/postgis/postgis/pull/108</a> (still seems<br>a bit to go so may not make an August cut without some loving)<br><br><br>Thanks,<br>Regina<br><br>_______________________________________________<br>postgis-devel mailing list<br><a href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/postgis-devel" target="_blank">http://lists.osgeo.org/mailman/listinfo/postgis-devel</a><o:p></o:p></p></blockquote></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div></div></body></html>