It is left open as the docs are not uploaded to source forge (in the release 
script).

I wonder if we need a "release" category or label in order to flag these kind 
of glitches. It is a good alternative to assigning them to Justin :)
-- 
Jody Garnett

On 14 August 2014 at 12:38:45 am, Ian Turton (ijtur...@gmail.com) wrote:

I think 6408 is actually fixed in that the docs do build but it was left open 
as a reminder to me that the docs need tidying up and updating when I next have 
some spare time. Feel free to close it and I'll add a new ticket to clean up 
the docs for later if you'd like.

Ian


On 14 August 2014 01:58, Jody Garnett <jody.garn...@gmail.com> wrote:
A quick pass through email resulted in the following:

- GEOS-6408 Building the PDF Docs fails 
- GEOS-6610 - Javadoc Download lacks CSS
- GEOS-6611 html docs download index and license files
- GEOS-6612 - Bin download ReadMe files out of data for java 7
- GEOS-6613 - Layer Preview format selector does not work on Safari
- GEOS-6602 Windows installer does not work on Windows 7
- GEOS-6588 GeoServer.app fails to start due to switch to Java 7

I thought some progress had been made on the use of OL3 ...
- GEOS-5748 Update OpenLayers to most recent stable version

Website: A reminder that we no longer need to upload the src archive, and it no 
longer linked to from the release_26 template. I set up templates for 
release_25 and release_26 allowing us to maintain links to previous source 
forge source downloads.
--
Jody Garnett

------------------------------------------------------------------------------

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel




--
Ian Turton
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to