<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Regina,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I’m looking at this release note, </div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><a href="https://github.com/postgis/postgis/blob/svn-trunk/HOWTO_RELEASE#L52-L57">https://github.com/postgis/postgis/blob/svn-trunk/HOWTO_RELEASE#L52-L57</a></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">on generating unpackaged SQL, and, ignoring the general ugliness, I can’t see how to accomplish it.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">The artifacts the step says it creates aren’t committed into the repo anywhere. The implication is that they are somehow generated before the packaging step, but it’s kind of weird that the step is before things like committing the tag, or altering the version numbers. What’s going on here?</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">P </div> <br><p style="color:#000;">On September 24, 2015 at 5:23:32 AM, Paragon Corporation (<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>I think it's too late for enhancements so I'm going to push all marked as enhancements or that sound too dangerous to do in 2.2 to 2.3.<br><br>-----Original Message-----<br>From: postgis-devel-bounces@lists.osgeo.org [mailto:postgis-devel-bounces@lists.osgeo.org] On Behalf Of Sandro Santilli<br>Sent: Thursday, September 24, 2015 5:23 AM<br>To: PostGIS Development Discussion <postgis-devel@lists.osgeo.org><br>Subject: Re: [postgis-devel] 2.2.0 RC 1<br><br>On Wed, Sep 23, 2015 at 12:02:15PM -0700, Paul Ramsey wrote:<br>> OK, I�m back from my travels, and the list of outstanding critical bugs is now very very short. Any objections to a first bundled release?<br><br>+1 for an RC1<br><br>But there are still 41 tickets open:<br>https://trac.osgeo.org/postgis/query?status=assigned&status=new&status=reopened&milestone=PostGIS+2.2.0&col=id&col=summary&col=status&col=type&col=priority&col=owner&col=component&order=owner<br><br>Please, owners, move out your tickets !<br><br>--strk;<br>_______________________________________________<br>postgis-devel mailing list<br>postgis-devel@lists.osgeo.org<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel<br><br><br>_______________________________________________<br>postgis-devel mailing list<br>postgis-devel@lists.osgeo.org<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel</div></div></span></blockquote> <div id="bloop_sign_1443101840061493760" class="bloop_sign"><div><br></div><span style="font-family:helvetica,arial;font-size:13px"></span>-- <br><span>http://postgis.net</span><div><span>http://cleverelephant.ca</span></div><div><br></div></div></body></html>