Customary warning that GeoServer release train is starting up.
I am scheduled to release GeoServer 2.3.3 shortly. When we checked in during monday’s meeting there are
failures with the CITE test infrastructure. Checking hudson we appear to be good to go.
Please let me know if you have any reason to hold up the release train, I do have a bit of flexibiity.
Please let me know if you have any reason to hold up the release train, I
do have a bit of flexibiity.
Starting the release 5 days before the official date in a monthly release
cycle seem a bit too
soon to me, but if that's the only window you have handy, go ahead
Customary warning that GeoServer release train is starting up.
I am scheduled to release GeoServer 2.3.3 shortly. When we checked in during monday’s meeting there are
failures with the CITE test infrastructure. Checking hudson we appear to be good to go.
Please let me know if you have any reason to hold up the release train, I do have a bit of flexibiity.
Starting the release 5 days before the official date in a monthly release cycle seem a bit too
soon to me, but if that’s the only window you have handy, go ahead
Customary warning that GeoServer release train is starting up.
I am scheduled to release GeoServer 2.3.3 shortly. When we checked in during monday’s meeting there are
failures with the CITE test infrastructure. Checking hudson we appear to be good to go.
Please let me know if you have any reason to hold up the release train, I do have a bit of flexibiity.
Starting the release 5 days before the official date in a monthly release cycle seem a bit too
soon to me, but if that’s the only window you have handy, go ahead
If anyone has a customer or community member to thank in the release notes please let me know!
Okay we have a successful CITE build:
+ cat geoserver/geoserver-2.3-SNAPSHOT/VERSION.txt
version = 2.3-SNAPSHOT
git revision = 897f681218e148157d70dc5c6b4aebf804683a2c
git branch = 897f681218e148157d70dc5c6b4aebf804683a2c
build date = 17-Jun-2013 03:41
geotools version = 9-SNAPSHOT
geotools revision = 9ef3b0bf6816ead05a01cd3e9a7b58586291b965
geowebcache version = 1.4-M20130509a
geowebcache revision = 05467ecca1592aa9b2dafc1f4aa5845650feea21
hudson build = 142
–
Jody Garnett
On Thursday, 13 June 2013 at 9:02 PM, Jody Garnett wrote:
Customary warning that GeoServer release train is starting up.
I am scheduled to release GeoServer 2.3.3 shortly. When we checked in during monday’s meeting there are
failures with the CITE test infrastructure. Checking hudson we appear to be good to go.
Please let me know if you have any reason to hold up the release train, I do have a bit of flexibiity.
So far testing is not going well:
- mac DMG did not show up for the party, mac zip i 61K
- windows zip will not work (351K)
The two platform specific zips are just intermediary steps to get to the
exe and dmg
(by mixing them with the bin archive), the two builds are managed by
OpenGeo internal
build servers and take some time to complete.
As far as I can tell you got the exe, the dmg is indeed still missing and
will require
someone at OpenGeo to kick it...
mac DMG did not show up for the party, mac zip i 61K
windows zip will not work (351K)
The two platform specific zips are just intermediary steps to get to the exe and dmg
(by mixing them with the bin archive), the two builds are managed by OpenGeo internal
build servers and take some time to complete.
As far as I can tell you got the exe, the dmg is indeed still missing and will require
someone at OpenGeo to kick it…
We are doing a server migration at the moment and the mac build server is actually down. I’ve built the dmg manually and uploaded it to the release directory on gridlock.
mac DMG did not show up for the party, mac zip i 61K
windows zip will not work (351K)
The two platform specific zips are just intermediary steps to get to the exe and dmg
(by mixing them with the bin archive), the two builds are managed by OpenGeo internal
build servers and take some time to complete.
As far as I can tell you got the exe, the dmg is indeed still missing and will require
someone at OpenGeo to kick it…
Okay blog post is up, I will send emails out shortly.
A couple of notes:
thanks to Justin for making the mac installer
the last time we published docs to the website was 2.3.0 - this step requires an OpenGeo staff member
the staging zip files for mac and windows installers were rsynced over to source forge
the pdf docs did not get generated (as such I removed the link from GeoServer 2.3.3 page)
–
Jody Garnett
On Thursday, 13 June 2013 at 9:02 PM, Jody Garnett wrote:
Customary warning that GeoServer release train is starting up.
I am scheduled to release GeoServer 2.3.3 shortly. When we checked in during monday’s meeting there are
failures with the CITE test infrastructure. Checking hudson we appear to be good to go.
Please let me know if you have any reason to hold up the release train, I do have a bit of flexibiity.
Okay blog post is up, I will send emails out shortly.
A couple of notes:
thanks to Justin for making the mac installer
the last time we published docs to the website was 2.3.0 - this step requires an OpenGeo staff member
the staging zip files for mac and windows installers were rsynced over to source forge
the pdf docs did not get generated (as such I removed the link from GeoServer 2.3.3 page)
–
Jody Garnett
On Thursday, 13 June 2013 at 9:02 PM, Jody Garnett wrote:
Customary warning that GeoServer release train is starting up.
I am scheduled to release GeoServer 2.3.3 shortly. When we checked in during monday’s meeting there are
failures with the CITE test infrastructure. Checking hudson we appear to be good to go.
Please let me know if you have any reason to hold up the release train, I do have a bit of flexibiity.
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
On 24 June 2013 07:13, Jody Garnett <jody.garnett@anonymised.com> wrote:
Okay blog post is up, I will send emails out shortly.
A couple of notes:
- thanks to Justin for making the mac installer
- the last time we published docs to the website was 2.3.0 - this step
requires an OpenGeo staff member
- the staging zip files for mac and windows installers were rsynced over
to source forge
- the pdf docs did not get generated (as such I removed the link from
GeoServer 2.3.3 page)
--
Jody Garnett
On Thursday, 13 June 2013 at 9:02 PM, Jody Garnett wrote:
Customary warning that GeoServer release train is starting up.
I am scheduled to release GeoServer 2.3.3 shortly. When we checked in
during monday's meeting there are
failures with the CITE test infrastructure. Checking hudson we appear to
be good to go.
Please let me know if you have any reason to hold up the release train, I
do have a bit of flexibiity.
--
Jody Garnett
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows: