[Geoserver-devel] [Geoserver-users] Setting hostname for IPVS environment

Hey all,

This is great, and is something I've had on my back burner for a while (we're using a proxied setup and the bum OnlineResourceURL's in our capdoc are goofing up folks trying to ingest our services).

We're running geoserver-trunk, however, and a thought occured to me. Is it up to each bug-fix to get itself fixed on both the trunk and the 1.4.x branch?

Meaning, if I fix something on trunk should I always try and be responsible and back-port the fix (if it's relevant) to 1.4.x? And is everyone doing bugfixes aware that they should be forward-porting their fixes to trunk?

Alternatively, is someone periodically merging 1.4.x to trunk to catch the fixes applied there?

Just trying to keep track of where effort should be expended.

thanks,
--saul

Chris Holmes wrote:

Hey, it's not super well documented and is a recent addition, so not too surprising you didn't find it. We should probably add it to the FAQ.

See: http://docs.codehaus.org/display/GEOSDOC/Configure+GeoServer+to+run+with+a+proxy

I believe for RC2 this should be accessible from the web admin tool, I think under Config -> Server

best regards,

Chris

Saul Farber ha scritto:

Hey all,

This is great, and is something I've had on my back burner for a while (we're using a proxied setup and the bum OnlineResourceURL's in our capdoc are goofing up folks trying to ingest our services).

We're running geoserver-trunk, however, and a thought occured to me. Is it up to each bug-fix to get itself fixed on both the trunk and the 1.4.x branch?

Meaning, if I fix something on trunk should I always try and be responsible and back-port the fix (if it's relevant) to 1.4.x? And is everyone doing bugfixes aware that they should be forward-porting their fixes to trunk?

If you fix something on trunk, you should backport the fix to 1.4.x too, yes, unless the fix is really hard to port back. If you're adding new
behaviour no need to back port thought.

Alternatively, is someone periodically merging 1.4.x to trunk to catch the fixes applied there?

I'm forward porting all changes that I do on 1.4.x on trunk as I commit them (so, I always double commit all the fixes to make sure fixes does
not get lost).

Cheers
Andrea Aime