Hi,
while I was doing the 1.7.5 release I made a review of the release
guide. I found a few topics worth discussing:
Here are the items:
- a paragraph talking about mails to gt2 devel and gs devel was
missing, I added it
- I also added a paragraph about the prerequisites (commit and
admin rights one has to have in order to make a release)
- there is no mention of the parallel gt2 release. From experience
the suggestion would be to tag gt2, run the cite, make the
necessary fixes, and once the cite work, release gt2
- the updated README step is first, but it requires a link to
the JIRA release notes. It is actually possible to make the
link beforehand, but that was not obvious to me at first,
so I added a comment
- some sed commands missed the -i flag
- the guide suggest to make the cite tests and the hand tests
after uploading the arftifacs to sf. What if the cite
do fail? Imho they should be run from the IDE
(assuming a totally clean checkout)
or from the release artifacts before the release.
(I haven't included this change in the attached patch)
- the sf file release system now allows a simple scp
upload in the form:
scp *.zip user@anonymised.com:uploads
which should be simple enough to follow for both windows
and linux users. Shall we replace the dav/sftp suggestions?
- the steps to make a release on sf changed again. Now one
has to go in Project Admin/Feature Settings, choose
the "manage" button in the "File Release System" row,
and then continue as usual. This is included in the
diff attached
- the last steps about announcements are a bit tricky.
I guess we do want to announce first on the blog,
which requires review, so those steps are to be
performed in the days after the release no?
Most of the changes above (minus the ones explicitly
excluded) are contained in the attached patch (the sf1.png
replaces the same named file in the dev guide).
The funny thing is that at the same time I edited a bit
the GeoTools release guide.. oh, boy, what a pain, working
with Sphinx is so much better 
And oh, here are the CITE tests results:
wfs 1.0 full pass
wfs 1.1 full pass (besides usual postgres 8.3 failure on like on dates)
wms 1.1 full pass
wcs 1.0 full pass
wcs 1.1 full pass
I did not manage to run the xlink tests thought, the h2
configuration does not work and it seems on 2.5.x the
spatialdb in a box functions were not ported over.
Oh well, I guess it's not much of an issue, xlink works
only in H2 anyways (or at least it was tested only there).
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
(attachments)
resguide.patch (3.31 KB)
Andrea Aime ha scritto:
Hi,
while I was doing the 1.7.5 release I made a review of the release
guide. I found a few topics worth discussing:
And oh, missed one important point: I cannot make the OSX
release, someone Mac-enabled will have to do it and upload
the artifact to Sourceforge.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Andrea Aime ha scritto:
Hi,
while I was doing the 1.7.5 release I made a review of the release
guide. I found a few topics worth discussing:
And oh, missed one important point: I cannot make the OSX
release, someone Mac-enabled will have to do it and upload
the artifact to Sourceforge.
Sure I can do that. And I applied your changes to the release guide (with some tweaks). Thanks Andrea.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Andrea Aime wrote:
Andrea Aime ha scritto:
Hi,
while I was doing the 1.7.5 release I made a review of the release
guide. I found a few topics worth discussing:
And oh, missed one important point: I cannot make the OSX
release, someone Mac-enabled will have to do it and upload
the artifact to Sourceforge.
Sure I can do that. And I applied your changes to the release guide (with some tweaks). Thanks Andrea.
Looked at the release guide this morning, it looks great.
I noticed a couple of things thought:
- the image I provided was not used, sf1.png still depicts the old
SF UI
- the part dealing with SF uploads is outdated and points to a sf
page that is no more there.
For the latter I did not actually provide a patch, but there was
some comments in my mail with a question:
-------------------------------------------------------------
- the sf file release system now allows a simple scp
upload in the form:
scp *.zip user@anonymised.com:uploads
which should be simple enough to follow for both windows
and linux users. Shall we replace the dav/sftp suggestions?
-------------------------------------------------------------
Mind if I change that part of the release guide to follow to
above suggestion?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Looked at the release guide this morning, it looks great.
I noticed a couple of things thought:
- the image I provided was not used, sf1.png still depicts the old
SF UI
- the part dealing with SF uploads is outdated and points to a sf
page that is no more there.
For the latter I did not actually provide a patch, but there was
some comments in my mail with a question:
-------------------------------------------------------------
- the sf file release system now allows a simple scp
upload in the form:
scp *.zip user@anonymised.com:uploads
which should be simple enough to follow for both windows
and linux users. Shall we replace the dav/sftp suggestions?
-------------------------------------------------------------
Mind if I change that part of the release guide to follow to
above suggestion?
Oops, missed that. Sure thing, make the changes as you see fit.
-Justin
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.