Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in publicly available docs about manifest branch #2332

Open
wants to merge 1 commit into
base: v0.14
Choose a base branch
from

Conversation

adamency
Copy link

@adamency adamency commented Mar 25, 2024

The branch published on the website is actually v0.14 but _index.md is using the same text as in the main branch misleading warning against using the displayed manifests.

Is this a BUG FIX or a FEATURE ?:

/kind documentation

What this PR does / why we need it:

The branch published on the website is actually v0.14 but _index.md is using the same text as in the main branch misleading warning against using the displayed manifests.

Special notes for your reviewer:

Release note:

NONE

@adamency
Copy link
Author

Added DCO Signed-off-by line

@cyclinder
Copy link
Contributor

Hi @adamency, It looks like you still don't pass the DCO check, please see:

Commit sha: [a604e4f](https://github.com/metallb/metallb/pull/2332/commits/a604e4f69ad645bfc0dcb70fcd3578f64409a37f), Author: Benjamin Habié, Committer: Benjamin Habié; Expected "Benjamin Habié [77821695+adamency@users.noreply.github.com](mailto:77821695+adamency@users.noreply.github.com)", but got "Benjamin Habié [adamency@protonmail.com](mailto:adamency@protonmail.com)".

The branch published on the website is actually v0.14 but `_index.md`
is using the same text as in the `main` branch misleading warning
against using the displayed manifests.

Signed-off-by: Benjamin Habié <adamency+github@protonmail.com>
@adamency
Copy link
Author

@cyclinder My apologies, the DCO is correctly passing now :)

@@ -75,7 +75,7 @@ If you want to deploy MetalLB using the [experimental FRR-K8s mode]({{% relref "
kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.3/config/manifests/metallb-frr-k8s.yaml
```

Please do note that these manifests deploy MetalLB from the main development branch. We highly encourage cloud operators to deploy a stable released version of MetalLB on production environments!
These manifests deploy MetalLB from a release branch. Indeed, we highly encourage cloud operators to deploy a stable released version of MetalLB (instead of manifests from the main branch) on production environments!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I finally got here. I think the right approach is just to remove this part as a whole, and it should be reomved from the main branch as it is the master where we generate all the versioned release notes using this script

def bumprelease(ctx, version, previous_version):

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @fedepaol, so do you mean to remove the line 78 entirely ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, as it sounds like a legacy bit from where we were not replacing main with the right tag after a release.

Copy link

This PR has been automatically marked as stale because it has been open 30 days
with no activity. This issue will be closed in 10 days unless you do one of the following:

  • respond or perform some activity on this PR
  • have one of these labels applied: hold

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants