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

Develop a gated process for MFE replacements #417

Open
jmakowski1123 opened this issue Aug 15, 2022 · 0 comments
Open

Develop a gated process for MFE replacements #417

jmakowski1123 opened this issue Aug 15, 2022 · 0 comments
Labels
epic Large unit of work, consisting of multiple tasks

Comments

@jmakowski1123
Copy link

Problem

There is too much of a lack of adherence to deprecation standards and it negatively impacts MFE workflows. In at least one case, a new MFE has replaced a pre-existing IDA without porting commonly used features. This has to be avoided in the future. There is often a lack of awareness among any Open edX user who did not initiate the deprecation process and thus may not be aware that it is happening.

Product/Platform Value

A more controlled process for releasing contingent on reimplementation will reduce, and ideally eradicate, the tech debt that currently hinders new feature development and maintenance.

Acceptance Criteria

A well documented workflow with stakeholder buy-in that implements a gated process where MFE replacements are only adopted for official release when the feature they replace has been properly reimplemented.

Related or in-progress work

Contingencies

@arbrandes arbrandes added the epic Large unit of work, consisting of multiple tasks label Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Large unit of work, consisting of multiple tasks
Projects
Status: Backlog
Development

No branches or pull requests

2 participants