Skip to content

Develop a gated process for MFE replacements #191

@jmakowski1123

Description

@jmakowski1123

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicLarge unit of work, consisting of multiple tasks

    Type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions