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 a policy for migration of algorithms to the legacy provider #67

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

nhorman
Copy link

@nhorman nhorman commented Apr 23, 2024

No description provided.

policies/legacy-migration.md Show resolved Hide resolved
policies/legacy-migration.md Show resolved Hide resolved
policies/legacy-migration.md Show resolved Hide resolved
policies/legacy-migration.md Outdated Show resolved Hide resolved
policies/legacy-migration.md Outdated Show resolved Hide resolved
policies/legacy-migration.md Outdated Show resolved Hide resolved

## Migration announcement mechanism
Announcements of migrations from a source provider to the Legacy provider is
made via the ALG-DEPRECATIONS.md file in the source code root directory for
Copy link
Member

Choose a reason for hiding this comment

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

This is an interesting idea to list the deprecations. Perhaps we should not confine this just to algorithms but to other things deprecated from now on?

Copy link
Author

Choose a reason for hiding this comment

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

I'm fine with expanding a deprecation list, sure. Maybe rename the file to DEPRECATIONS.md, and have a section for legacy migrations, as well as sections for any other distinct deprecation in the future?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, that's what I meant.

policies/legacy-migration.md Outdated Show resolved Hide resolved
policies/legacy-migration.md Outdated Show resolved Hide resolved
policies/legacy-migration.md Outdated Show resolved Hide resolved
@nhorman nhorman requested a review from t8m April 23, 2024 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write a proposed policy on moving algorithms to the legacy provider
2 participants