Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

Switch audio media status from 'beta' to 'supported' #1315

Closed
7 of 9 tasks
zackkrida opened this issue Apr 22, 2022 · 2 comments · Fixed by #1801
Closed
7 of 9 tasks

Switch audio media status from 'beta' to 'supported' #1315

zackkrida opened this issue Apr 22, 2022 · 2 comments · Fixed by #1801
Assignees
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon

Comments

@zackkrida
Copy link
Member

zackkrida commented Apr 22, 2022

When audio is fully supported and out of beta, we should switch the MediaStatus to 'supported' to remove the beta button from the audio item in the content switcher.

Milestone

https://github.com/WordPress/openverse-frontend/milestone/16

API-related issues

Catalog-related issues

  • WordPress/openverse-catalog#558
  • WordPress/openverse-catalog#263
  • WordPress/openverse-catalog#658

Others (Not blocking the milestone)

  • WordPress/openverse#142
  • WordPress/openverse-api#716
@zackkrida zackkrida added 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature 🕹 aspect: interface Concerns end-users' experience with the software labels Apr 22, 2022
@krysal krysal added 🟨 priority: medium Not blocking but should be addressed soon and removed 🟩 priority: low Low priority and doesn't need to be rushed labels May 2, 2022
@krysal krysal removed the 🚧 status: blocked Blocked & therefore, not ready for work label Jul 8, 2022
@zackkrida
Copy link
Member Author

Hmm, as far as deployment is concerned should this be feature-flagged instead of hardcoded?

@krysal
Copy link
Member

krysal commented Sep 2, 2022

I'm fine with either way, could be feature-flagged to release it quickly though maybe it will simplify code if we removed it completely (?)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants