<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>I agree that we don't release with those tickets open. </div><div><br></div><div>But why branch before release and wait a week? </div><div><br></div><div>/Nicklas</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757">Sent from my Samsung device</div></div><br><br>-------- Original message --------<br>From: Sandro Santilli <strk@keybit.net> <br>Date: 03/10/2015 08:29 (GMT+01:00) <br>To: PostGIS Development Discussion <postgis-devel@lists.osgeo.org> <br>Subject: Re: [postgis-devel] 2.2.0 Release <br><br>On Fri, Oct 02, 2015 at 01:59:25PM -0700, Paul Ramsey wrote:<br>> We’ve had a week of RC1, can we release? The only thing I could see leaning towards no would be integrating the fix to the bounding circle code <https://trac.osgeo.org/postgis/ticket/2996> , which is extensive, and doing RC2 to provide testing time. Please indicate your preference…<br><br>I think we should have an empty list of tickets targetting<br>Milestone 2.2.0 before shipping next tarball.<br><br>There are 9 at this moment (one of which marked as "critical"):<br><br>https://trac.osgeo.org/postgis/query?status=assigned&status=new&status=reopened&milestone=PostGIS+2.2.0&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&order=priority<br><br>An old rule we had was: final ships after one week of _no_activity_<br>in the release branch. How about creating the 2.2 branch togheter<br>with RC2 once the trac milestone is clean ?<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></body></html>