Robert Raposa

[inform] This DEPR is in the Draft state. It can't move forward without a DEPR coordinator to help update it to match the updated DEPR template. No action is required,...

Not sure if this is a separate issue, but it may be that that the hash caching that we use to avoid doing npm related install can get into a...

[inform] @justinhynes reported having this issue "not running local" (remote desktop?) and successfully used the following workaround: ``` Run npm ci and then paver update_assets from an LMS shell. ```...

The following workaround worked for at least 2 developers: ``` 1. Enter LMS shell (make lms-shell). 2. npm ci 3. paver update_assets ``` It has been noted that `paver install_prereqs`,...

@jristau1984: Could we use observability to confirm if we have any usage of the deprecated code?

[inform/request] This ticket was accepted under the old DEPR process. The [updated Process States in OEP-21](https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0021-proc-deprecation.html#process-states) help add clarity to communications and timing regarding the introduction of breaking changes. This...

Thanks @regisb. I’ll take this to our teams because: 1. I’m not aware of us needing to do this for our plugin, and maybe that is just personal lack of...

@regisb: What is the status of this PR? Do you know how it relates to any changes that might be happening in terms of "devstack" => "development", or do we...

@kdmccormick: Is this ready to land as-is? Will it need to be updated in the future? Thank you.

Ideas: - Just update the troubleshooting doc. - Add a private list of additional repos for the devstack commands to update.