<HTML dir=ltr><HEAD><TITLE>[postgis-devel] autobuild cleanup</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.5626" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText78470 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Kevin,</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>In general I agree with you that non-version tagged (except for SVN) should be available as prebuilt tars.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>The 1.3.4 seems to be very popular though since it has JSON and some other minor nice enhancements and is not riske.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I think we are in a bit of an odd situation in the sense that the SVN is probably too SVNish except for the bravest of brave and people are forced to go to SVN to get the 1.3.4</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Would be nice if we could have the 1.3.4 tar available for download. But if that's a lot of trouble, I suppose we could live with not having it. </FONT><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> postgis-devel-bounces@postgis.refractions.net on behalf of Kevin Neufeld<BR><B>Sent:</B> Fri 9/12/2008 1:40 PM<BR><B>To:</B> PostGIS Development Discussion<BR><B>Subject:</B> [postgis-devel] autobuild cleanup<BR></FONT><BR></DIV></DIV>
<DIV>
<P><FONT size=2>Just so I'm clear on a few things...<BR><BR>1. The PostGIS documentation website<BR>(<A href="http://postgis.refractions.net/documentation">http://postgis.refractions.net/documentation</A>) has a link to the 1.3<BR>version documentation. This is actually built from the 1.3 branch<BR>(currently 1.3.4), NOT the last stable tagged release 1.3.3. Is this<BR>really what we want? The Downloads section does not have a link to<BR>postgis-1.3.4.tar.gz, only the latest stable tagged releases. This is<BR>noticeable if you look at the 1.3 manual<BR>(<A href="http://postgis.refractions.net/documentation/manual-1.3/">http://postgis.refractions.net/documentation/manual-1.3/</A>), the download<BR>link in section 2.2 is broken. I don't think we should be referencing<BR>non-tagged versions (except svn trunk of course) ... but that's just my<BR>two cents.<BR><BR>2. If the issue in #1 is fixed to reference the last stable release,<BR>then the autobuild for 1.3 can simply be to checkout and build the code<BR>and email parties responsible for breaking it. I can remove the 1.3<BR>documentation update and code tarballing for postgis-1.3.4.<BR><BR>3. Once the above is resolved, the generated PDF doc should be the same<BR>version as the html.<BR><BR>Thoughts?<BR>-- Kevin<BR>_______________________________________________<BR>postgis-devel mailing list<BR>postgis-devel@postgis.refractions.net<BR><A href="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR></FONT></P></DIV></BODY></HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>