mirror of https://github.com/cncf/toc.git
Fix links in propoals/reviews
This fixes the links in our proposals and reviews to the new location for the graduation criteria and project proposal pages. Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
This commit is contained in:
parent
98347ced0e
commit
5e7495555f
|
|
@ -11,7 +11,7 @@ To highlight some of the achievements:
|
|||
- Adoptors: 1000+ (including commercial users and community users)
|
||||
- 4.0 GA released in May, 2020
|
||||
|
||||
On behalf of the maintainers team, we believe TiKV is ready for [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#graduation-stage).
|
||||
On behalf of the maintainers team, we believe TiKV is ready for [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#graduation-stage).
|
||||
|
||||
## Graduation State Criteria
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Since joining the CNCF in [July 2018](https://www.cncf.io/blog/2018/07/31/cncf-to-host-harbor-in-the-sandbox/) as a Sandbox project and in [November 2018](https://www.cncf.io/blog/2018/11/13/harbor-into-incubator/) moving to an Incubating Project, Harbor has built a healthy ecosystem of users, maintainers, and production implementations.
|
||||
|
||||
On behalf of the maintainers team, we believe Harbor is ready for the CNCF [Graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#graduation-stage) and meets the v1.2 criteria. We address the [CNCF Technical Due Diligence questions](tbd) in a separate Google Docs document (referred to as the `Tech-DD` from now on).
|
||||
On behalf of the maintainers team, we believe Harbor is ready for the CNCF [Graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#graduation-stage) and meets the v1.2 criteria. We address the [CNCF Technical Due Diligence questions](tbd) in a separate Google Docs document (referred to as the `Tech-DD` from now on).
|
||||
|
||||
*Name of project:* Harbor
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Helm originally joined the CNCF when Kubernetes became the first CNCF project. Helm was a sub-project of Kubernetes at that time. Since joining the CNCF as an incubating sister project to Kubernetes in June 2018, Helm has released v3, created a governance appropriate for Helm, and has continued to watch the use of Helm grow and evolve.
|
||||
|
||||
On behalf of the maintainers, we believe Helm is ready for [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#graduation-stage) and meets the v1.3 criteria. The Helm [due diligence questions](https://docs.google.com/document/d/1-5ncwLwikeQrAmeVAPuCYlWLYMCw2OmQuouTYCECYFk/edit), following the [guidelines](https://github.com/cncf/toc/blob/master/process/due-diligence-guidelines.md), can be found in a separate Google Docs document.
|
||||
On behalf of the maintainers, we believe Helm is ready for [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#graduation-stage) and meets the v1.3 criteria. The Helm [due diligence questions](https://docs.google.com/document/d/1-5ncwLwikeQrAmeVAPuCYlWLYMCw2OmQuouTYCECYFk/edit), following the [guidelines](https://github.com/cncf/toc/blob/master/process/due-diligence-guidelines.md), can be found in a separate Google Docs document.
|
||||
|
||||
Helm has seen dramatic growth since joining incubation. For example,
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Hi,
|
||||
|
||||
We would like to propose to donate LitmusChaos to CNCF as a SandBox project. We have been advised to follow the new process outlined [here](https://github.com/cncf/toc/blob/master/process/project_proposals.adoc). The template we are following is outlined [here](https://github.com/cncf/toc/issues/344).
|
||||
We would like to propose to donate LitmusChaos to CNCF as a SandBox project. We have been advised to follow the new process outlined [here](https://github.com/cncf/toc/blob/master/process/project_proposals.md). The template we are following is outlined [here](https://github.com/cncf/toc/issues/344).
|
||||
|
||||
Please consider this proposal and guide us through the process.
|
||||
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ This architecture is illustrated in the following diagram:
|
|||
|
||||
|
||||
## Formal Requirements
|
||||
Here is k3s's status on [the formal requirements](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#sandbox-stage)
|
||||
Here is k3s's status on [the formal requirements](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#sandbox-stage)
|
||||
- Require 3 of the 11 TOC members to step forward as sponsors to enter the sandbox - Pending
|
||||
- Adopt the CNCF Code of Conduct - [k3s is adopting the CNCF Community Code of Conduct](https://github.com/rancher/k3s/pull/1783)
|
||||
- Adhere to CNCF IP Policy (including trademark transferred) - We agree to this policy and will work through the requirements with the CNCF as the process moves forward
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
For TOC Consideration: please adopt Keylime into CNCF as a SandBox project.
|
||||
This proposal is being made in accordance with the [**stated
|
||||
process**](https://github.com/cncf/toc/blob/master/process/project_proposals.adoc) and the
|
||||
process**](https://github.com/cncf/toc/blob/master/process/project_proposals.md) and the
|
||||
[**proposal template**](https://github.com/cncf/toc/issues/344).
|
||||
|
||||
Authors: - Luke Hinds, @lukehinds, Red Hat, Keylime Project Lead
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Hello,
|
||||
|
||||
We would like to propose to donate Kuma to CNCF as a SandBox project. We are opening this GitHub issue according to the process outlined [here](https://github.com/cncf/toc/blob/master/process/project_proposals.adoc) with the format outlined [here](https://github.com/cncf/toc/issues/344).
|
||||
We would like to propose to donate Kuma to CNCF as a SandBox project. We are opening this GitHub issue according to the process outlined [here](https://github.com/cncf/toc/blob/master/process/project_proposals.md) with the format outlined [here](https://github.com/cncf/toc/issues/344).
|
||||
|
||||
Authors:
|
||||
|
||||
|
|
@ -148,7 +148,7 @@ More information can be accessed from the official documentation: https://kuma.i
|
|||
|
||||
# Formal Requirements
|
||||
|
||||
**_Document that the project fulfills the requirements as documented in the [CNCF graduation criteria for sandbox](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#sandbox-stage)_**
|
||||
**_Document that the project fulfills the requirements as documented in the [CNCF graduation criteria for sandbox](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#sandbox-stage)_**
|
||||
|
||||
* We [have adopted](https://github.com/Kong/kuma/blob/master/CODE_OF_CONDUCT.md) the CNCF Code of Conduct.
|
||||
* Will adhere to the CNCF IP policy.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
For TOC Consideration: please adopt PARSEC into CNCF as a SandBox project. This proposal is being
|
||||
made in accordance with the [**stated
|
||||
process**](https://github.com/cncf/toc/blob/master/process/project_proposals.adoc) and the
|
||||
process**](https://github.com/cncf/toc/blob/master/process/project_proposals.md) and the
|
||||
[**proposal template**](https://github.com/cncf/toc/issues/344).
|
||||
|
||||
Authors: - Paul Howard, @paulhowardarm, Arm Limited, PARSEC technical lead
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# Thanos Incubation Stage Proposal
|
||||
|
||||
During Thanos presentation at the [CNCF TOC meeting on 7/9/2019](https://docs.google.com/presentation/d/1jhzJlSAAJNNil1nIYp60eSMH3LPd6AwqHLt3vEAzMSg/edit#slide=id.g5cdf155fc3_0_4)
|
||||
we were suggested by TOC members to apply straight for [the Incubation Stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage).
|
||||
we were suggested by TOC members to apply straight for [the Incubation Stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage).
|
||||
We all agreed back then that we will join Sandbox first and after that perform Due Diligence required for the Incubation Stage.
|
||||
|
||||
This proposal aims to address the Diligence requirements.
|
||||
|
|
|
|||
|
|
@ -124,7 +124,7 @@ These goals translate to multiple specific work items, including:
|
|||
office hours. We would like all these types of project support to continue.
|
||||
|
||||
- Do you think that your project meets the [criteria for
|
||||
incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
- We believe that the project is in a healthy growing status in both user
|
||||
adoption and contributors. We are working to properly document existing
|
||||
|
|
|
|||
|
|
@ -171,7 +171,7 @@ Network Service Mesh had [two releases](https://networkservicemesh.io/docs/relea
|
|||
enthusiastically, or we have been informed cannot be provided until we reach incubation or graduation as a matter of
|
||||
policy set by the Board and/or TOC.
|
||||
|
||||
7. _Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?_
|
||||
7. _Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?_
|
||||
|
||||
Network Service Mesh does not currently meet all criteria for incubation, but is on track to do so.
|
||||
|
||||
|
|
|
|||
|
|
@ -143,7 +143,7 @@ KubeEdge falls in the scope of [CNCF Runtime SIG](https://github.com/cncf/sig-ru
|
|||
- We need more speaking and marketing opportunities to help attract more contributors and user adoptions.
|
||||
- We also need some technical writers to help improve documentation and website content.
|
||||
|
||||
* Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
* Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
- Yes, incubation proposal is under preparation.
|
||||
|
||||
## Project Links
|
||||
|
|
|
|||
|
|
@ -161,7 +161,7 @@ Areas of future collaboration with the Rook community may include:
|
|||
- Embracing and communicating the use of Kubernetes in ways that may not have been originally anticipated or intended by the originators of Kubernetes, including as a substrate for a fundamentally new way of managing data and delivering storage capabilities. For example, it may be useful to increasingly use a phrase such as Container Attached Storage to reflect this pattern.
|
||||
- Additional help with reviewing licenses used by sub components. There may need to be a check if the licenses of these subcomponents - most notably CDDL - can be included in the CNCF whitelist policy or if these sub components should be held in another open source repository such as an OpenSource repository of MayaData or otherwise.
|
||||
|
||||
- *Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?*
|
||||
- *Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?*
|
||||
|
||||
Yes. We are in the process of completing the Due Diligence document and submitting the incubation proposal.
|
||||
|
||||
|
|
|
|||
|
|
@ -115,6 +115,6 @@ This is a tremendous help for us and supports us in making autoscaling simpler.
|
|||
|
||||
### Incubation
|
||||
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
Yes, we do, and we are planning to propose to graduate later this month/next month and is being tracked on [GitHub](https://github.com/kedacore/governance/issues/2).
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ Some areas where we can use help are:
|
|||
|
||||
## Incubation
|
||||
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
Yes. The Kyverno project team has started planning a proposal for incubation and plans to submit it in the next month. This work is tracked in [issue #2838](https://github.com/kyverno/kyverno/issues/2838).
|
||||
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@ Parsec will continue to look towards the CNCF for guidance in preparing itself f
|
|||
|
||||
## Readiness for Incubation
|
||||
|
||||
Parsec does not yet meet the [stated criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc#incubating-stage) for incubation for the following reasons:
|
||||
Parsec does not yet meet the [stated criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md#incubating-stage) for incubation for the following reasons:
|
||||
|
||||
- There are not yet three independent adoptions that are in production.
|
||||
- Security assessment still pending.
|
||||
|
|
|
|||
|
|
@ -78,6 +78,6 @@ We think there are two important ways that CNCF can help us with the growth of t
|
|||
|
||||
## Incubation
|
||||
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
Yes, we believe that Artifact Hub is ready and we now have [an issue](https://github.com/artifacthub/hub/issues/1418) to track progress at proposing a move to incubation.
|
||||
|
|
|
|||
|
|
@ -357,7 +357,7 @@ the project with the following:
|
|||
## Incubation
|
||||
|
||||
> Do you think that your project meets the [criteria for
|
||||
> incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
> incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
Yes, we very much believe Crossplane meets the criteria for incubation and have published the
|
||||
proposal on March 22, 2021. We have presented to the App-Delivery TAG, published a full and
|
||||
|
|
|
|||
|
|
@ -136,7 +136,7 @@ but we are open to other suggestions, even some coaching/tips about reaching out
|
|||
|
||||
## Incubation
|
||||
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc#incubating-stage)?
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
No, at this point we don't feel that the project meets the criteria.
|
||||
We would like to grow more in terms of maintainers and known users before considering to move to the next stage.
|
||||
|
|
|
|||
|
|
@ -198,7 +198,7 @@ We want to achieve the above roadmap while also maintaining cadence with upstrea
|
|||
|
||||
The CNCF has been helpful thus far by contributing CI resources. As we worked towards incubation, we'll likely reach out with specific, tactical asks as we encounter them.
|
||||
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
At this time, we aren't ready to submit for incubation status. Our goal is to submit next year. We'll use this upcoming year to prep for that and improve the areas of the project that need it.
|
||||
|
||||
|
|
|
|||
|
|
@ -183,7 +183,7 @@ For our releases, Keptn maintainers follow the [release checklist](https://githu
|
|||
- The CNCF ecosystem is another driver for Keptn. We are already engaging with multiple CNCF projects and will further drive collaboration with the help of the CNCF.
|
||||
|
||||
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
- Yes, we've also filed our [incubation proposal](https://github.com/cncf/toc/pull/670).
|
||||
|
||||
|
|
|
|||
|
|
@ -116,7 +116,7 @@ What we've shipped since:
|
|||
- We would like to reintroduce a way to follow feature usage and installation count as it's hard to track adoption without this.
|
||||
- We could use with some help with some technical writing.
|
||||
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
No for the following reasons:
|
||||
|
||||
|
|
|
|||
|
|
@ -192,7 +192,7 @@ on the board.
|
|||
- As part of the project goals for the upcoming year, there is increased collaboration planned with other CNCF projects (in terms of providing a joint solution/integration as
|
||||
well as help them by enabling project(app)-specific experiments). A forum to ease these interactions or present findings jointly would be much beneficial.
|
||||
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
### Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
Yes, we've also filed our [incubation proposal](https://github.com/cncf/toc/pull/569).
|
||||
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@ We are looking forward to the continued support in the above areas and as well a
|
|||
|
||||
### Incubation
|
||||
|
||||
**Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?**
|
||||
**Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?**
|
||||
|
||||
Yes, we do, and we are planning to present the progress we have made since our last [CNCF Storage TAG review](https://github.com/cncf/toc/pull/506#issuecomment-756153457) and move towards the next steps.
|
||||
|
||||
|
|
|
|||
|
|
@ -145,7 +145,7 @@ Volcano falls in the scope of [CNCF Runtime SIG](https://github.com/cncf/sig-run
|
|||
- We need more speaking and marketing opportunities to help attract more contributors and user adoptions.
|
||||
- We also need some technical writers to help improve documentation and website content.
|
||||
|
||||
* Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
* Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
- Yes, incubation proposal is under preparation.
|
||||
|
||||
## Project Links
|
||||
|
|
|
|||
|
|
@ -152,7 +152,7 @@ Network Service Mesh had three release in the last year:
|
|||
enthusiastically, or we have been informed cannot be provided until we reach incubation or graduation as a matter of
|
||||
policy set by the Board and/or TOC.
|
||||
|
||||
7. _Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?_
|
||||
7. _Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?_
|
||||
|
||||
Network Service Mesh does not currently meet all criteria for incubation, but is on track to do so.
|
||||
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@ Some areas where we'd like to get continued and additional help are:
|
|||
|
||||
## Incubation
|
||||
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage)?
|
||||
> Do you think that your project meets the [criteria for incubation](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#incubating-stage)?
|
||||
|
||||
Not at this time. It's the goal of the Schemahero project to continue to build in the Sandbox for the next year to increase production-grade adoption and add additional maintaining organizations. Once the project has achieved production status and has moved out of evaluation phases at adopting organizations, we will start planning for incubation.
|
||||
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ Importantly, we also received the donation of the [`aws-privateca-issuer`](https
|
|||
|
||||
In the short term, a major goal is to complete the migration of the [jetstack/cert-manager](https://github.com/jetstack/cert-manager) repo into the [cert-manager organization](https://github.com/cert-manager/).
|
||||
|
||||
After that, the guiding star will be to target CNCF [incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc#incubating-stage), since we believe cert-manager to be a strong candidate for incubation.
|
||||
After that, the guiding star will be to target CNCF [incubation](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md#incubating-stage), since we believe cert-manager to be a strong candidate for incubation.
|
||||
|
||||
We also aim to grow our support for new features and tools in the cloud native ecosystem; recent and ongoing examples include the [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) and the Kubernetes [CertificateSigningRequest](https://kubernetes.io/docs/reference/access-authn-authz/certificate-signing-requests/) resource. We're always on the lookout for more in this space.
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ Put more generally, we ideally don't want to reinvent the wheel when it comes to
|
|||
|
||||
## Incubation
|
||||
|
||||
Based on the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc#incubating-stage), cert-manager seems to already tick the relevant boxes required for incubation. We believe cert-manager to be a strong candidate for incubation based on the following:
|
||||
Based on the [graduation criteria](https://github.com/cncf/toc/blob/main/process/graduation_criteria.md#incubating-stage), cert-manager seems to already tick the relevant boxes required for incubation. We believe cert-manager to be a strong candidate for incubation based on the following:
|
||||
|
||||
- Document that it is being used successfully in production by at least three independent end users
|
||||
cert-manager is used in production by _many_ more than three independent end users; it shouldn't be hard to find a few case studies if needed. Several major cloud native projects including [Istio](https://istio.io/latest/docs/ops/integrations/certmanager/), the [Kubernetes Cluster API](https://cluster-api.sigs.k8s.io/developer/guide.html#cert-manager) and [Knative](https://knative.dev/development/install/serving/installing-cert-manager/) suggest or require that cert-manager be installed.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ Since the [March 2017 announcement](https://www.cncf.io/announcement/2017/03/29/
|
|||
|
||||
In late 2017, containerd announced its [1.0 release](https://blog.docker.com/2017/12/cncf-containerd-1-0-ga-announcement/), followed in early 2018 by a 1.1 release that has been updated with several minor fix releases through 2018. The containerd team has just completed the next major release, [1.2.0](https://github.com/containerd/containerd/releases/tag/v1.2.0), with more complete Windows runtime support and a new runtime shim v2 API that is [proving](https://www.cncf.io/blog/2018/09/17/gsoc-18-kata-containers-support-for-containerd/) [valuable](https://twitter.com/resouer/status/1035066629887905792) for [runc](https://github.com/opencontainers/runc) alternatives like [Kata containers](https://katacontainers.io/).
|
||||
|
||||
At this time, we believe containerd is ready for the [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#graduation-stage) within the CNCF, and per the guidelines listed there, we detail our readiness in the section below.
|
||||
At this time, we believe containerd is ready for the [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#graduation-stage) within the CNCF, and per the guidelines listed there, we detail our readiness in the section below.
|
||||
|
||||
### CNCF Graduation Criteria
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ time of acceptance) for details on the acceptance criteria at the time of those
|
|||
In the time since being accepted to the incubation stage, Rook has demonstrated healthy growth of
|
||||
the community, continually released new features, and expanded storage provider support. This
|
||||
proposal focuses on Rook's maturity and compliance with the [CNCF Graduation Criteria
|
||||
v1.3](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc).
|
||||
v1.3](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md).
|
||||
|
||||
Every major project and community statistic has [**increased
|
||||
2-3x**](https://docs.google.com/presentation/d/1mMPYMDC4JMGWhoL3FzFgeasSLJepNwYMfwQD-T_gET4/edit#slide=id.g3e2163a66f_0_0)
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Since joining the CNCF in [February 2018](https://www.cncf.io/blog/2018/02/05/cncf-host-vitess/) as an incubation project, Vitess has built a healthy ecosystem of maintainers and production adoptions.
|
||||
|
||||
On behalf of the maintainers team, we believe Vitess is ready for [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#graduation-stage) and meets the v1.2 criteria. As the criteria has evolved since February 2018, we include also answers for incubation criteria and address [due dilligence questions](https://docs.google.com/document/d/1TDlRdgfTiEWunpav-G8gkaQF7Zk84-9tNAXyv1I0Kws/edit) in a separate Google Docs document.
|
||||
On behalf of the maintainers team, we believe Vitess is ready for [graduation stage](https://github.com/cncf/toc/blob/master/process/graduation_criteria.md#graduation-stage) and meets the v1.2 criteria. As the criteria has evolved since February 2018, we include also answers for incubation criteria and address [due dilligence questions](https://docs.google.com/document/d/1TDlRdgfTiEWunpav-G8gkaQF7Zk84-9tNAXyv1I0Kws/edit) in a separate Google Docs document.
|
||||
|
||||
### CNCF Incubation Criteria
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue