[Geoserver-devel] Pulls for WPS changes and fixes

GeoServer GeoServer Developer
1

I’m starting to put my pull requests up for a series of changes and fixes for WPS.

Here’s the first;

PR: https://github.com/geoserver/geoserver/pull/1305

issue: https://osgeo-org.atlassian.net/browse/GEOS-7281

This is a very simple fix to resolve an issue shown by the Python Scripting language module for WPS processes. Processes aren’t being moved to RUNNING state (i.e. when they don’t have any arguments/parameters).

Should I send a message to list for every pull request?

Thanks,
Dave

2

Thanks Dave, generally only message the list if you need specific review/feedback. There is no need to double up on email and pull request communication.

You may also wish to add a comment to your pull request mentioning a specific party needed for a review (for example mentioning Mike for a documentation change).

···

On 27 October 2015 at 15:50, Dave Blasby <dblasby@anonymised.com> wrote:

I’m starting to put my pull requests up for a series of changes and fixes for WPS.

Here’s the first;

PR: https://github.com/geoserver/geoserver/pull/1305

issue: https://osgeo-org.atlassian.net/browse/GEOS-7281

This is a very simple fix to resolve an issue shown by the Python Scripting language module for WPS processes. Processes aren’t being moved to RUNNING state (i.e. when they don’t have any arguments/parameters).

Should I send a message to list for every pull request?

Thanks,
Dave

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

–
Jody Garnett