[postgis-devel] autobuild cleanup

[Kevin Neufeld]

Ok, fair enough.

This implies that I should add a postgis-1.3.4.tar.gz to the download 
site that gets updated regularly along with the html and pdf 
documentation, right?  In this way, the download urls in Chapter 2.2 
will match the PostGIS download site.

Is the 1.3.4 branch then still considered to be the last "stable" 
release even though it may break from a bad commit?  Perhaps the website 
should be expanded to have:

Last stable release
   [html | pdf]
Current release branch
   [html | pdf]
Current SVN head
   [html | pdf]
Portugues Documentation
PostGIS Wiki

Maybe that's too much, I don't know.

-- Kevin


Paul Ramsey wrote:
> I actually like building off the stable branch rather than tags,
> because documentation fixes are relevant right away. If someone finds
> a syntax error in an example, it is nice to roll that out immediately,
> rather than have that fix be invisible until the next point release.
> The only "downside" is the version number not perfectly matching,
> which I've been able to live with.
> 
> P.
> 
> On Fri, Sep 12, 2008 at 10:40 AM, Kevin Neufeld
> <kneufeld at refractions.net> wrote:
>> Just so I'm clear on a few things...
>>
>> 1. The PostGIS documentation website
>> (http://postgis.refractions.net/documentation) has a link to the 1.3 version
>> documentation.  This is actually built from the 1.3 branch (currently
>> 1.3.4), NOT the last stable tagged release 1.3.3.  Is this really what we
>> want?  The Downloads section does not have a link to postgis-1.3.4.tar.gz,
>> only the latest stable tagged releases.  This is noticeable if you look at
>> the 1.3 manual (http://postgis.refractions.net/documentation/manual-1.3/),
>> the download link in section 2.2 is broken.  I don't think we should be
>> referencing non-tagged versions (except svn trunk of course) ... but that's
>> just my two cents.
>>
>> 2. If the issue in #1 is fixed to reference the last stable release, then
>> the autobuild for 1.3 can simply be to checkout and build the code and email
>> parties responsible for breaking it.  I can remove the 1.3 documentation
>> update and code tarballing for postgis-1.3.4.
>>
>> 3. Once the above is resolved, the generated PDF doc should be the same
>> version as the html.
>>
>> Thoughts?
>> -- Kevin
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel