From 0f04dd52d10b31a98418d7fe53ca7344119aaba5 Mon Sep 17 00:00:00 2001 From: Kyle McCormick Date: Thu, 9 May 2024 11:12:32 -0400 Subject: [PATCH] build: do not tag this in the named open edx release (#239) This repo has been "maybe" for a while, but it has not been tagged yet. This commit removes the "maybe", we simply will not tag it, since it isn't clear from the README or the ADRs how this microservice could be used by an Open edX site operator. According to OEP-10: > To be included in an Open edX release, a component must meet these criteria. > * ... > * It must be installable in at least one of the supported installation methods. > * It must be usable in the installed configuration. This decision can always be reversed in the future by adding a release branch to catalog-info.yaml --- openedx.yaml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/openedx.yaml b/openedx.yaml index 1000a6c8..401fcf4a 100644 --- a/openedx.yaml +++ b/openedx.yaml @@ -13,9 +13,3 @@ oeps: oep-18: true oep-30: state: true -openedx-release: - # The openedx-release key is described in OEP-10: - # https://open-edx-proposals.readthedocs.io/en/latest/oep-0010-proc-openedx-releases.html - # The FAQ might also be helpful: https://openedx.atlassian.net/wiki/spaces/COMM/pages/1331268879/Open+edX+Release+FAQ - maybe: true # Delete this "maybe" line when you have decided about Open edX inclusion. - ref: main