WFS 2.0 revision 1.32 in Beta

lgoltz commented 5 years ago

dstenger commented 5 years ago

[x] The master branch should contain the latest "stable" version. Make sure all verified pull requests are merged.
[x] Make sure it builds properly running mvn clean install site.
[x] Test locally the master branch with the reference implementation, if there is one.
- If it is OK, continue, if not create or update an issue, in the issue tracker of that test.
[x] Review closed issues to be included in the release.
- Update title if appropriate.
- Tag, if they are not tagged with the milestone number.
[x] Update release notes, usually the file is at src/site/markdown/relnotes.md.
- Add a new title for the revision, if there is not one already.
- Copy the issues to be included in the release, link and title.
- Add any other highlights.
[x] Create a new issue in the OGC release tracker and set label approved-by-test-lead.
- Write a title for the issue should containing: [Abbreviation] [version] revision [revision] in Beta. For example: WFS 1.1 revision 1.23 in Beta. It should always be in Beta. OGC staff will create the issue related to making the releases in the production, official web site.

dstenger commented 5 years ago

[x] In the OGC release tracker assign the issue to a milestone.
[x] Check that the issues and pull requests in the ETS issue tracker are properly written and associated to the correct milestone. Make sure issues are closed in the ETS issue tracker.
Do the release. Process involves creating a revision based on the pom.xml version, updating the GitHub page, tag, and updating the revision on the pom for the next release.
- [x] Check if Maven configuration has been updated: How to create Releases with Maven.
- [x] Create release with Jenkins.
[x] Close milestone in the ETS issue tracker.
[x] Set label ready-for-installation.

opengeospatial / te-releases