chore: update history structure for conformance reports

Signed-off-by: Shane Utt <[email protected]>

Author: shaneutt

conformance/reports/cilium.yaml renamed to conformance/reports/v0.7.1/cilium-cilium.yaml

@@ -1,6 +1,6 @@
 apiVersion: gateway.networking.k8s.io/v1alpha1
 date: "2023-07-24T14:26:14-07:00"
-gatewayAPIVersion: 4c436290f2bfeaeaf0b1a367449e16de3e0addc4
+gatewayAPIVersion: 4c436290f2bfeaeaf0b1a367449e16de3e0addc4 # making an exception to the version for this release, since this was the first release we started submitting reports for.
 implementation:
   contact:
   - '@istio/maintainers'

conformance/reports/istio.yaml renamed to conformance/reports/v0.7.1/istio.io-istio.yaml

@@ -0,0 +1 @@
+latest

conformance/reports/kong-kubernetes-ingress-controller.yaml renamed to conformance/reports/v0.7.1/kong-kubernetes-ingress-controller.yaml

@@ -1,6 +1,6 @@
 apiVersion: gateway.networking.k8s.io/v1alpha1
 date: "2023-07-25T22:11:56Z"
-gatewayAPIVersion: "e9859d057b43d177176a9d3d6b15dbdd27fe7e46"
+gatewayAPIVersion: "e9859d057b43d177176a9d3d6b15dbdd27fe7e46" # making an exception to the version for this release, since this was the first release we started submitting reports for.
 implementation:
   contact:
   - '@projectcontour/maintainers'

conformance/reports/kuma.yaml renamed to conformance/reports/v0.7.1/kumahq-kuma.yaml

@@ -522,12 +522,28 @@ profiles:
 
 Implementers can submit their reports upstream by creating a pull request to
 the Gateway API repository and adding new reports to a file specific to their
-implementation's project name:
+implementation's organization and project name:
 
 ```console
-conformance/reports/<organization>-<project>.yaml
+conformance/reports/<version>/<organization>-<project>.yaml
 ```
 
+The `<version>` directory in the above refers to the version of Gateway API. The
+`latest` release will include a symlink that points to the latest version
+directory.
+
+For instance:
+
+```console
+conformance/reports/v0.7.1/acme-operator.yaml
+```
+
+> **NOTE**: Implementations **MUST** report for a specific release version
+> (e.g. `v0.7.1`) and not use branches or Git SHAs. Some exceptions will be
+> made for initial reports to help make it easier for implementations to get
+> started, but as we move to standard everyone should be reporting on specific
+> releases.
+
 Creating a pull request to add the `ConformanceReport` will start the
 [certification process](#certification-process).