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

Add documentation to maintain historical version config mappings #1686

Open
ayildirim21 opened this issue Apr 18, 2024 · 1 comment
Open
Assignees
Labels
area/sdk enhancement New feature or request

Comments

@ayildirim21
Copy link
Member

Summary

As per #1683 (comment). We should also in the same file mention that version_mapping.go should be updated after each new release.

Use Cases

After a release, in case developer did not know which files to update.


Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@ayildirim21 ayildirim21 added the enhancement New feature or request label Apr 18, 2024
@KeranYang
Copy link
Member

We should also in the same file mention that version_mapping.go should be updated after each new release.

I think it would be better that mention it in the releasing.md file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sdk enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants