prepping for 1.1.0-beta release

- Updating and documenting changelog creation process.
  antsibull-changelog was chosen because it is the standard tooling
  recommended by Ansible developers.
- Documenting the release process and several others so others can perform it in the
  future.
- Updating the integration tests to test against 2.13, which the 1.1.0
  final release will be certified for.
- Created changelog and update galaxy.yaml for 1.1.0-beta, which will be
  the next release.

Author: toumorokoshi

.github/workflows/ansible-integration-tests.yml

@@ -19,8 +19,7 @@ jobs:
     strategy:
       matrix:
         ansible_version:
-          # - stable-2.13
-          - stable-2.11
+          - stable-2.13
     steps:
       - name: check out code
         uses: actions/checkout@v2
@@ -29,7 +28,7 @@ jobs:
       - name: Set up Python
         uses: actions/setup-python@v1
         with:
-          python-version: '3.8'  # this is the minimum version required for Ansible 2.11
+          python-version: '3.8'  # this is the minimum version required for Ansible 2.13
       - name: Install dependencies
         run: pip install -r requirements.txt
       - name: Install ansible-base (${{ matrix.ansible_version }})

.github/workflows/ansible-test.yml

@@ -39,6 +39,7 @@ jobs:
         ansible_version:
           - stable-2.13
           - stable-2.11
+          - stable-2.9
     steps:
       - name: check out code
         uses: actions/checkout@v2

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "esbonio.sphinx.confDir": ""
+}

CHANGELOG.rst

@@ -0,0 +1,27 @@
+==========================
+Google.Cloud Release Notes
+==========================
+
+.. contents:: Topics
+
+
+v1.1.0-beta.0
+=============
+
+Minor Changes
+-------------
+
+- GCE inventory plugin - a new option ``name_suffix``, to add a suffix to the name parameter.
+
+Bugfixes
+--------
+
+- Disk has been fixed to send the sourceSnapshot parameter.
+- gcp_cloudtasks_queue - was not functional before, and is now functional.
+- gcp_compute_* - these resources use the correct selflink (www.googleapis.com) as the domain, no longer erroneously reporting changes after an execution.
+- gcp_compute_backend_service - no longer erroneously reports changes after an execution for ``capacity_scaler``.
+- gcp_container_cluster - support GKE clusters greater than 1.19+, which cannot use basic-auth.
+- gcp_crypto_key - skip_initial_version_creation defaults to the correct value.
+- gcp_iam_role - now properly undeletes and recognizes soft deleted roles as absent.
+- gcp_spanner_database - recognize a non-existent resource as absent.
+- gcp_storage_object - fix for correct version of dependency requirement.

CONTRIBUTING.md

@@ -4,6 +4,7 @@
 
 1. [Clone the repository](#cloning).
 1. Make the desired code change.
+1. Add a [changelog fragment](https://docs.ansible.com/ansible/devel/community/development_process.html#changelogs-how-to) to describe your change.
 1. [Run integration tests locally and ensure they pass](running-integration-tests).
 1. Create a PR.
 
@@ -86,4 +87,15 @@ If the linting fails, that is generally due to `ansible-lint`, which can be run
 
 ```
 ansible-lint
-```
+```
+
+## Specific Tasks
+
+The following enumerates detailed documentation for specific tasks related tot
+the codebase.
+
+### Updating the supported ansible-core version
+
+1. modify the [ansible-integration-tests.yaml](.github/workflows/ansible-integration-tests.yml) to the version of ansible-core that you would like to test against.
+1. (optional) update the version of ansible-core version required in [meta/runtime.yaml](meta/runtime.yml).
+

MAINTAINING.md

@@ -1,5 +1,10 @@
 # Maintainer Documentation
 
+## See CONTRIBUTING.md for more tasks
+
+[CONTRIBUTING.md](./CONTRIBUTING.md) contains more instructions that could
+apply to contributors and not just maintainers (e.g. update ansible-core version).
+
 ## CI GCP Project Configuration
 
 To enable running integration tests, a test GCP project must be provided.
@@ -13,3 +18,51 @@ There is a Google-maintained CI project, `ansible-gcp-ci`, that is used for this
 Since running the full set of integration tests requires the usage of GCP
 credentials which are stored as a secret, maintainers must verify that tests pass the integration test run that runs on push to the master branch after accepting a change.
 
+## Release Process
+
+### Overview
+
+The process is as follows:
+
+1. Update the version of the collection.
+1. Update the changelog.
+2. Create a GitHub release to tag the repo and begin the publishing process.
+
+### Steps
+
+#### Update Collection Version
+
+Modify the [galaxy.yaml](./galaxy.yml) file to the desired collection version:
+
+```yaml
+version: {NEW_VERSION}
+```
+
+Ansible collection versions [must follow SEMVER](https://docs.ansible.com/ansible/devel/dev_guide/developing_collections_distributing.html#collection-versions).
+
+Alpha / beta releases are optional.
+
+#### Update the changelog
+
+Providing a valid [CHANGELOG.rst](./CHANGELOG.rst) is required for a certifiable
+collection release.
+
+Use the [antsibull-changelog](https://github.com/ansible-community/antsibull-changelog)
+tool to generate the changelog:
+
+```sh
+pip install antsibull-changelog
+antsibull-changelog release
+```
+
+This will remove all the changelog fragments from ./changelogs/fragments and
+merge them into CHANGELOG.rst.
+
+### Tag a release
+
+The release process is mostly automated, relying on GitHub releases and the following
+workflows:
+
+- [publish to Ansible Galaxy](./.github/workflows/pythonpublish.yml).
+- [publish to Automation Hub](./.github/workflows/automationhub.yml).
+