You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ chance to try to fix the issue before it is exploited in the wild.
15
15
16
16
Helm v4 development takes place on the `main` branch while Helm v3 is on the `dev-v3` branch.
17
17
18
-
Helm v3 will continue to receive bug fixes and updates for new Kubernetes releases until July 8th 2026. Security enhancement will still be applied until November 11th 2026. See the blog <https://helm.sh/blog/helm-4-released#helm-v3-support> for more details.
18
+
Helm v3 will continue to receive bug fixes and updates for new Kubernetes releases until July 8th 2026. Security enhancements will still be applied until November 11th 2026. See the blog <https://helm.sh/blog/helm-4-released#helm-v3-support> for more details.
19
19
20
20
Bugs should first be fixed on Helm v4 and then backported to Helm v3. Helm v3 (and the `dev-v3` branch) is no longer accepting new features.
21
21
@@ -162,9 +162,9 @@ There are 5 types of issues (each with their own corresponding [label](#labels))
162
162
for future reference. Generally these are questions that are too complex or large to store in the
163
163
Slack channel or have particular interest to the community as a whole. Depending on the
164
164
discussion, these can turn into `feature` or `bug` issues.
165
-
-`proposal`: Used for items (like this one) that propose a new ideas or functionality that require
165
+
-`proposal`: Used for items (like this one) that propose new ideas or functionality that require
166
166
a larger community discussion. This allows for feedback from others in the community before a
167
-
feature is actually developed. This is not needed for small additions. Final word on whether
167
+
feature is actually developed. This is not needed for small additions. Final word on whether
168
168
a feature needs a proposal is up to the core maintainers. All issues that are proposals should
169
169
both have a label and an issue title of "Proposal: [the rest of the title]." A proposal can become
0 commit comments