-
Notifications
You must be signed in to change notification settings - Fork 392
kubernetes sig-release Discussions
Sort by:
Latest activity
Discussions
-
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 🙏 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💡 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 -
You must be logged in to vote 💬 Socializing SLSA level 3 and higher requirements
kind/featureCategorizes issue or PR as related to a new feature. sig/releaseCategorizes an issue or PR as relevant to SIG Release. needs-priority -
You must be logged in to vote 💡 Simplify the release process by removing Code Thaw
kind/featureCategorizes issue or PR as related to a new feature. sig/releaseCategorizes an issue or PR as relevant to SIG Release. priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.