Kyle McCormick

The new implementation won't be landing in Palm, most likely. I pushed the acceptance date out to May 3rd, and pushed the final removal out to Redwood.

This deprecation has been Accepted. Development of the replacement asset script is ongoing (see issues linked in description). When the replacement is ready, I'll put a warning in the output...

The new asset processing suite has been merged as "experimental". I will continue to test it, and will communicate when it's time to mark the Paver assets suite as deprecated...

I am hoping to mark the old asset build as deprecated in Quince so we can remove it in Redwood, although the content libraries V2 project is competing for my...

@feanil As I alluded to earlier, carrying out this DEPR will allow us to circumvent libsass-python's Python API (which isn't compatible with Python>3.9) and instead go straight to the underlying...

This has renewed urgency, since the Python 3.8->3.12 upgrade is blocked by libsass-python. This must be resolved well ahead of the Redwood cutoff (late April). Here is my updated plan:...

UPDATE: This PR switches the old `paver` static asset build commands to be simple wrappers around `npm run` commands, with instructive deprecation warnings: * https://github.com/openedx/edx-platform/pull/34318. This prepares us to drop...

I am rolling this DEPR into a larger proposed deprecation of all edx-platform Paver usage: https://github.com/openedx/edx-platform/issues/34467

Thanks @DanielVZ96 ! When you're ready for review, let me know.

Thanks @DanielVZ96 . Your code looks good to me. Through no fault of your own, we're currently wading through a couple different bugs around Library Content duplication and copying ([one...