OGC API Processes 1.0 revision 0.1 in Beta

[dstenger]

Prepare release (for each test suite individually)

• [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 -Pintegration-tests,docker.
• [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]

@bpross-52n Can you please help us preparing the first release of this test suite by completing above checklist (please also see https://github.com/opengeospatial/cite/wiki/Releasing-Tests-and-TEAM-Engine#test-lead-release-checklist)?

[dstenger]

Create release (for each test suite individually)

• [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.

[dstenger]

Created SSH key on Jenkins server. However, it was not possible to apply it to the GitHub repository as I do not have the permissions.

[dstenger]

Release job was created: http://build.opengeospatial.org/jenkins/view/release/job/ets-ogcapi-processes10-release/

[dstenger]

Tried to create branch gh-pages:

stenger@elsbeere:~/git/ets-ogcapi-processes10$ git switch --orphan gh-pages
Zu neuem Branch 'gh-pages' gewechselt
stenger@elsbeere:~/git/ets-ogcapi-processes10$ git commit --allow-empty -m "Initial commit"
[gh-pages (Root-Commit) 3b3639c] Initial commit
stenger@elsbeere:~/git/ets-ogcapi-processes10$ git push -u origin gh-pages
ERROR: Permission to opengeospatial/ets-ogcapi-processes10.git denied to dstenger.
fatal: Konnte nicht vom Remote-Repository lesen.

Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen
und das Repository existiert.

Write permissions to the repository are missing.

[dstenger]

@ghobona Can you please give me permissions for the GitHub repository https://github.com/opengeospatial/ets-ogcapi-processes10 so that I can upload the key and push branches?

[dstenger]

@bpross-52n I realized that dependency ets-common version 10-SNAPSHOT is used as the parent of this project. Unfortunately, Snapshot versions are not allowed in releases. Is it possible to downgrade this dependency to the latest release of ets-common (version 9)?

[ghobona]

@dstenger You now have write permissions.

[bpross-52n]

@bpross-52n I realized that dependency ets-common version 10-SNAPSHOT is used as the parent of this project. Unfortunately, Snapshot versions are not allowed in releases. Is it possible to downgrade this dependency to the latest release of ets-common (version 9)?

@dstenger Sorry, I downgraded the dependency.

[dstenger]

@ghobona Unfortunately, I can still not upload the deploy key needed by Jenkins. I probably require admin permissions for that (please see other ets repos).

[dstenger]

@bpross-52n I also had to set the value of property docker.teamengine.version to 5.4.1: https://github.com/opengeospatial/ets-ogcapi-processes10/commit/55d0565293360dbc63134679d79a41e7d92aa3fb

[dstenger]

Tried to create branch gh-pages:

stenger@elsbeere:~/git/ets-ogcapi-processes10$ git switch --orphan gh-pages
Zu neuem Branch 'gh-pages' gewechselt
stenger@elsbeere:~/git/ets-ogcapi-processes10$ git commit --allow-empty -m "Initial commit"
[gh-pages (Root-Commit) 3b3639c] Initial commit
stenger@elsbeere:~/git/ets-ogcapi-processes10$ git push -u origin gh-pages
ERROR: Permission to opengeospatial/ets-ogcapi-processes10.git denied to dstenger.
fatal: Konnte nicht vom Remote-Repository lesen.

Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen
und das Repository existiert.

Write permissions to the repository are missing.

Branch gh-page could now be successfully created.