| /dports/www/py-spyne/spyne-2.13.16/doc/source/ |
| H A D | history.rst | 8 Versioning section in Development History
50 spyne-2.10.10
57 spyne-2.10.9
66 spyne-2.10.8
74 spyne-2.10.7
80 spyne-2.10.6
85 spyne-2.10.5
95 spyne-2.10.4
102 spyne-2.10.3
109 spyne-2.10.2
[all …]
|
| /dports/www/grafana8/grafana-8.3.6/packages/ |
| H A D | README.md | 5 ## Versioning section in Grafana frontend packages
17 ### Stable releases
23 ### Alpha and beta releases
27 ### Automatic prereleases
59 ### Manual release
78 ### Building individual packages
86 ### Setting up @grafana/\* packages for local development
|
| /dports/net/gscloud/gscloud-0.11.0/vendor/k8s.io/client-go/ |
| H A D | README.md | 47 ### Versioning subsection
57 #### Branches and tags.
67 #### Compatibility: your code <-> client-go
75 #### Compatibility: client-go <-> Kubernetes clusters
84 #### Compatibility matrix
141 #### Deprecation policy
148 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/security/vault/vault-1.8.2/vendor/k8s.io/client-go/ |
| H A D | README.md | 46 ### Versioning subsection
56 #### Branches and tags.
66 #### Compatibility: your code <-> client-go
74 #### Compatibility: client-go <-> Kubernetes clusters
83 #### Compatibility matrix
134 #### Deprecation policy
141 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/devel/gitlab-runner/gitlab-runner-8925d9a06fd8e452e2161a768462652a2a13111f/vendor/github.com/docker/cli/cli-20.10.2/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
146 #### Deprecation policy
153 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/devel/gitlab-runner/gitlab-runner-8925d9a06fd8e452e2161a768462652a2a13111f/vendor/github.com/containerd/containerd/containerd-1.4.3/vendor/k8s.io/client-go/ |
| H A D | README.md | 46 ### Versioning subsection
56 #### Branches and tags.
66 #### Compatibility: your code <-> client-go
74 #### Compatibility: client-go <-> Kubernetes clusters
83 #### Compatibility matrix
136 #### Deprecation policy
143 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/istio/istio-1.6.7/vendor/github.com/containerd/containerd/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
146 #### Deprecation policy
153 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/helm/helm-3.5.2/vendor/github.com/containerd/containerd/vendor/k8s.io/client-go/ |
| H A D | README.md | 46 ### Versioning subsection
56 #### Branches and tags.
66 #### Compatibility: your code <-> client-go
74 #### Compatibility: client-go <-> Kubernetes clusters
83 #### Compatibility matrix
136 #### Deprecation policy
143 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/security/aws-iam-authenticator/aws-iam-authenticator-0.5.2/vendor/k8s.io/client-go/client-go-0.16.8/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
146 #### Deprecation policy
153 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/docker/docker-ce-18.09.5/components/cli/vendor/k8s.io/client-go/ |
| H A D | README.md | 44 ### Versioning subsection
63 #### Branches and tags.
75 #### Compatibility: your code <-> client-go
83 #### Compatibility: client-go <-> Kubernetes clusters
92 #### Compatibility matrix
141 #### Deprecation policy
148 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/chaoskube/chaoskube-0.22.0/vendor/k8s.io/client-go/ |
| H A D | README.md | 46 ### Versioning subsection
56 #### Branches and tags.
66 #### Compatibility: your code <-> client-go
74 #### Compatibility: client-go <-> Kubernetes clusters
83 #### Compatibility matrix
138 #### Deprecation policy
145 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/net-mgmt/prometheus2/prometheus-2.30.3/vendor/k8s.io/client-go/ |
| H A D | README.md | 39 ### Versioning subsection
49 #### Branches and tags.
59 #### Compatibility: your code <-> client-go
67 #### Compatibility: client-go <-> Kubernetes clusters
76 #### Compatibility matrix
133 #### Deprecation policy
140 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/misc/concourse/concourse-6.7.2/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
144 #### Deprecation policy
151 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/go-wtf/wtf-0.21.0/vendor/k8s.io/client-go/client-go-12.0.0/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
145 #### Deprecation policy
152 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/net-mgmt/thanos/thanos-0.11.0/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
145 #### Deprecation policy
152 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/helm/helm-3.5.2/vendor/github.com/docker/cli/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
146 #### Deprecation policy
153 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/security/vault/vault-1.8.2/vendor/github.com/containerd/containerd/vendor/k8s.io/client-go/ |
| H A D | README.md | 46 ### Versioning subsection
56 #### Branches and tags.
66 #### Compatibility: your code <-> client-go
74 #### Compatibility: client-go <-> Kubernetes clusters
83 #### Compatibility matrix
136 #### Deprecation policy
143 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/misc/concourse/concourse-6.7.2/vendor/github.com/containerd/containerd/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
146 #### Deprecation policy
153 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/gomplate/gomplate-3.9.0/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
144 #### Deprecation policy
151 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/helm/helm-3.5.2/vendor/k8s.io/client-go/ |
| H A D | README.md | 46 ### Versioning subsection
56 #### Branches and tags.
66 #### Compatibility: your code <-> client-go
74 #### Compatibility: client-go <-> Kubernetes clusters
83 #### Compatibility matrix
138 #### Deprecation policy
145 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/devel/gitlab-runner/gitlab-runner-8925d9a06fd8e452e2161a768462652a2a13111f/vendor/k8s.io/client-go/client-go-0.21.1/ |
| H A D | README.md | 47 ### Versioning subsection
57 #### Branches and tags.
67 #### Compatibility: your code <-> client-go
75 #### Compatibility: client-go <-> Kubernetes clusters
84 #### Compatibility matrix
141 #### Deprecation policy
148 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/www/grafana8/grafana-8.3.6/vendor/k8s.io/client-go/ |
| H A D | README.md | 39 ### Versioning subsection
49 #### Branches and tags.
59 #### Compatibility: your code <-> client-go
67 #### Compatibility: client-go <-> Kubernetes clusters
76 #### Compatibility matrix
133 #### Deprecation policy
140 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/istio/istio-1.6.7/vendor/k8s.io/client-go/ |
| H A D | README.md | 46 ### Versioning subsection
56 #### Branches and tags.
66 #### Compatibility: your code <-> client-go
74 #### Compatibility: client-go <-> Kubernetes clusters
83 #### Compatibility matrix
134 #### Deprecation policy
141 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/sysutils/terraform/terraform-1.0.11/vendor/k8s.io/client-go/ |
| H A D | README.md | 45 ### Versioning subsection
64 #### Branches and tags.
76 #### Compatibility: your code <-> client-go
84 #### Compatibility: client-go <-> Kubernetes clusters
93 #### Compatibility matrix
145 #### Deprecation policy
152 #### Why do the 1.4 and 1.5 branch contain top-level folder named after the version?
|
| /dports/devel/pecl-ast/ast-1.0.16/ |
| H A D | README.md | 500 ### 90 (current)
506 ### 85 (stable)
512 ### 80 (stable)
522 ### 70 (stable)
532 ### 60 (stable)
541 ### 50 (stable)
|