Hi,
been working on pushing out the RC2. Here are some notes and feedback.
Builds
------------------------------------------------------------
We need to setup new new hudson builds for the 2.0.x branch, both continous and nightly
Documentation
---------------------------
The PDF build failed
* the instructions for building the html docs won't generate two
separate folders, user and devel, inside the zip file, but mix that
probably overwrites some files.
I already made some other fixes that I still need to commit to the
release docs, but as far as I can see to get the desired results
one has to actually make somewhere the user/devel folders and
copy the build files over. Is this right?
* I could not make the pdf, it failed with the errors attached
to this mail (pdf-errror.txt)
Build artifacts
------------------------------------
The biz size is at 50MB, there are some suspect libraries that
will need to be checked:
2.0M webapps/geoserver/WEB-INF/lib/fop-0.94.jar
196K webapps/geoserver/WEB-INF/lib/bcmail-jdk14-138.jar
1.5M webapps/geoserver/WEB-INF/lib/bcprov-jdk14-138.jar
The gml datastore has been removed, it's not part of GeoTools
anymore (removed due to lack of maintainership).
Interactive build checks
-------------------------------------
* We miss various demos we had in 1.7.x timeframe, GeoRSS,
WFS-T, WMS Overlay with commercial layers
* The Google Earth instructions assume regionation, which has
been turned off by default. Also, GE 5.0 on Linux it's broken,
so I could not test it out that much.
* During the startup there are a couple of catalog related
exceptions about duplicated coverages, but they seem harmless
Publishing the artifacts
--------------------------------------------------------
* FRS changed again... now we directly upload files to SFTP
and it's done, but we also have to created directories
As far as I can see the best path is to go and separate
extensions and main artifacts on the local file system,
something like:
mkdir extensions
mv *plugin.zip extensions
mv web-security*.zip extensions
Create a release-notes-2.0-RC1.txt file in the current folder with
the release notes, and then SFTP into sourceforge and do something
along the lines of:
sftp user,geoserver@anonymised.com
cd /home/frs/project/g/ge/geoserver/GeoServer
mkdir 2.0-RC1
put *.zip
put release-notes.txt
cd ../..
cd "GeoServer Extensions"
mkdir 2.0-RC1
lcd extensions
put *.zip
bye
Then go into the SourceForge file manager and mark the release
notes file as being a release note: locate the file, click on
it, a popup will allow to mark it as such.
The same popup allows one to mark the file as platform specific,
thought it seems to allow to mark a single file as being
good for a certain platform, which does not really matches our
reality (two installers for windows, two platform independent
files, the bin and the war).
Wondering if marking the platform file is going to do us any
good, the main entry point for downloads is our custom page
at geoserver.org anyways?
Ah, once the files have been uploaded to SF there will be a
delay before they show up in the file browser. They say 15
minutes... hmmm... been waiting for longer here...
They showed immediately on the admin "file browser" but
so far not on the public one
* the page template needs to be updated: the sf release number is
no more around, the gml download neither.
The release notes have to be uploaded as a file as far as I can
see now so the link in the template should be modified accordingly.
The end
----------------------------------------
I'll be updating the release guide tomorrow, the other activities
need to be ticketed and the release artifacts (when they'll show
up) will need to be checked.
Justin is building the OSX installer afaik.
Any takers for the rest?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
(attachments)
pdf-error.txt (4.08 KB)
