Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On 22/12/15 02:21, Andrea Aime wrote: > If you have doubts other have made mistakes No, just a discussion of how to check in the context of a manual Jira release. I am happy for a release manager to check any fixVersions I set. I am just suggesting one way it might be done. > So yes, the

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On Mon, Dec 21, 2015 at 12:33 PM, Ben Caradoc-Davies wrote: > I see no tag for 2.7.5 in GitHub nor a call for artifact testing. Are you > sure this issue was omitted? In the release procedure, release in Jira is > the first step. If the steps were performed out of order and

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies wrote: > Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira > makes is far too easy for an administrator to inadvertently add a > version); someone has an issue for it: >

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

Ian, yes, the Jira API changed when we moved from Codehaus and the Python script is broken. Not as smooth as your last releases in 2014. The undocumented manual procedure is to for each project: - Manually perform the release in Administration / Versions and release the version using the

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On 22/12/15 00:21, Andrea Aime wrote: > On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies > wrote: >> Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira >> makes is far too easy for an administrator to inadvertently add a >> version); someone has an issue

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

And this is what I recommend when encountering issues with an unexpected fixVersion: On 22/12/15 00:16, Ben Caradoc-Davies wrote: > so check GitHub commits to confirm -- Ben Caradoc-Davies Director Transient Software Limited New Zealand