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 "..." on the right-hand side - Create the next unreleased version for the series (13.6 and 2.7.6 in your case. - Search for problematic fixVersions, that is, Unresolved issues (Open, In Progress, or Reopened) for the released version and read the comments. Was the issue really resolved for this version? If so, leave the fixVersion, otherwise remove it. fixVersion means was fixed; this is not an aspirational field. If you are really puritanical you can check all issues to make sure no Resolved issues were Won't-Fix: these should have no fixVersions. This is more than the script ever did but is worth the effort for a good quality changelog. And on maintenance the effort is tiny. GeoTools 13.5: https://osgeo-org.atlassian.net/projects/GEOT/versions/12000 For this issue with fixVersion 13.5 Torben wrote: "I was not able to backport to 13.x due to API incompatibility." so remove 13.5 from fixVersions (you can also search the git log of 13.x for the issue): https://osgeo-org.atlassian.net/browse/GEOT-5318 GeoServer 2.7.5: https://osgeo-org.atlassian.net/projects/GEOS/versions/11902 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: https://osgeo-org.atlassian.net/browse/GEOS-7353 Comment here suggests Andrea backported to 2.7.x, so check GitHub commits to confirm and change the fixVersion from 2.7.6 to 2.7.5: https://github.com/geoserver/geoserver/pull/1375 All the issues for 2.7.5 are resolved so just release the version and you have your changelog. Kind regards, Ben. On 21/12/15 21:19, Ian Turton wrote: > It seems that both GeoTools and GeoServer's release-jira jobs fail (and > have been failing for 9 and 6 months) - I assume this is related to the > change of jira hosting, is there a new script or manual step that I need to > run before hitting publish for the new releases? > > Cheers > > Ian > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > GeoTools-Devel mailing list > geotools-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > -- Ben Caradoc-Davies <b...@transient.nz> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
