List view
- Due by October 28, 2025•7/7 issues closed
- Due by July 22, 2025•14/14 issues closed
- Due by April 22, 2025•3/3 issues closed
- Due by January 21, 2025•12/12 issues closed
- Due by July 23, 2024•13/13 issues closed
- Due by April 23, 2024•13/13 issues closed
- Due by January 23, 2024•10/10 issues closed
- No due date•2/2 issues closed
- No due date•1/1 issues closed
- Due by October 24, 2023•21/21 issues closed
- Due by July 25, 2023•11/11 issues closed
- Due by April 25, 2023•5/5 issues closed
- Due by January 24, 2023•10/10 issues closed
- No due date•2/2 issues closed
- Due by July 12, 2022•4/4 issues closed
- Due by May 31, 2022•8/8 issues closed
- Due by August 23, 2022•6/6 issues closed
- Due by April 19, 2022•12/12 issues closed
- Due by March 8, 2022•8/8 issues closed
- Due by January 25, 2022•10/10 issues closed
- Due by December 14, 2021•6/6 issues closed
- Due by November 2, 2021•1/1 issues closed
- Due by September 21, 2021•5/5 issues closed
- Due by August 10, 2021•4/4 issues closed
- Due by June 29, 2021•3/3 issues closed
- Due by May 18, 2021•5/5 issues closed
- Due by April 6, 2021•10/10 issues closed
- Due by February 23, 2021
- Due by January 12, 2021•3/3 issues closed
- Due by November 10, 2020•6/6 issues closed
- Due by September 29, 2020•10/10 issues closed
- Due by August 18, 2020•9/9 issues closed
- Due by July 7, 2020•22/22 issues closed
- Due by May 26, 2020•9/9 issues closed
- Due by April 14, 2020•24/24 issues closed
- Due by March 3, 2020•7/7 issues closed
- Due by January 21, 2020•4/4 issues closed
- Due by December 10, 2019•5/5 issues closed
The Serving release after 0.9.x. Final name TBD ( https://github.com/knative/community/pull/26 )
Due by October 29, 2019•5/5 issues closedThe ambition of 0.8 is to be a release candidate for a "v1" of serving.
Due by August 6, 2019•45/45 issues closed- Due by June 25, 2019•33/33 issues closed
- Due by May 14, 2019•44/44 issues closed
- Due by April 2, 2019•47/47 issues closed
- Due by February 19, 2019•50/50 issues closed
Milestone for bucketing things that need further triage by the WG leads.
No due date•84/84 issues closedThis milestone is used to hold issues that are in scope for "v1", but have not yet been pulled into an earlier milestone (e.g. 0.3). The intent of this milestone is to enable WG leads and the ToC to scope what a "v1" would look like, and burn down towards "v1" by pulling items into our cadence of 0.X milestones.
No due date•121/121 issues closed- Due by January 8, 2019•42/42 issues closed