<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 10.00.9200.16660"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial>That is right. We only have the development branched
docs on the website. The 2.1.0 one is in the doc download links we
had on the announce.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial>Apologies for the link being broken. For release emails
I suually copy from teh CMS.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial>For the postgis.net website we are using PieCrust as
our CMS and while I love PieCrust, it has this annoying habit of eating my
_ unless I escape them.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial>I forgot to escape that particular one. I tried markdown
but it sometimes works and sometimes eats my _ as
well.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial>If anyone has a solution to the pie crust eating _ problem,
I'm all ears.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=192441116-24082013><FONT color=#0000ff
size=2 face=Arial>Regina</FONT></SPAN></DIV><BR>
<DIV lang=en-us class=OutlookMessageHeader dir=ltr align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> postgis-users-bounces@lists.osgeo.org
[mailto:postgis-users-bounces@lists.osgeo.org] <B>On Behalf Of
</B>BladeOfLight16<BR><B>Sent:</B> Friday, August 23, 2013 10:39
PM<BR><B>To:</B> PostGIS Users Discussion<BR><B>Cc:</B> PostGIS Development
Discussion<BR><B>Subject:</B> Re: [postgis-users] PostGIS 2.1.0
released<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr>
<DIV class=gmail_extra>
<DIV class=gmail_quote>nOn Sat, Aug 17, 2013 at 9:46 PM, Paragon Corporation
<SPAN dir=ltr><<A href="mailto:lr@pcorp.us"
target=_blank>lr@pcorp.us</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV><snip><BR></DIV></BLOCKQUOTE>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV> </DIV></BLOCKQUOTE>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Users
of 1.5 and below will need to go the hard-upgrade path documented
in<BR>manual:<BR><A
href="http://postgis.net/docs/manual-2.1/postgisinstallation.html#hardupgrade"
target=_blank>http://postgis.net/docs/manual-2.1/postgisinstallation.html#hardupgrade</A><BR></BLOCKQUOTE>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV><BR></DIV>
<DIV><snip> <BR></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>That link is broken. The correct link appears to be <A
href="http://postgis.net/docs/manual-2.1/postgis_installation.html#hard_upgrade">http://postgis.net/docs/manual-2.1/postgis_installation.html#hard_upgrade</A>.
Although, the main page for that version of the manual (<A
href="http://postgis.net/docs/manual-2.1/">http://postgis.net/docs/manual-2.1/</A>)
says it's the "PostGIS 2.1.1dev Manual". Can someone confirm that's the right
link, as this is no longer a dev version?<BR><BR>Thanks for this awesome piece
of software.<BR></DIV></DIV></DIV></DIV></BODY></HTML>