[DEPR-2U] Paver

[robrap]

2U follow-up

• Original DEPR: [DEPR]: Paver openedx/edx-platform#34467

ACs:

• Remove references and usages of paver in both the configuration and devstack repositories.
• Verify that there are no other usages of it in the edx org.

[jristau1984]

@dianakhuang are you able to break out the steps needed to complete the AC above? We would like Arbi-BOM to do the work, but having the tasks clear is a first step.

[dianakhuang]

@jristau1984 added some ACs. I that's not detailed enough, I can add some more details when I get a chance.

[robrap]

• I find it helpful if there is always an accompanying comment when moving to blocked that explains why a ticket is blocked.
• Kyle posted a warning in the #cc-edx-platform channel that removal of Paver could come as early as tomorrow. I'm unclear if we are prepared for that change or not.
• Here are the results of a search for paver in the edx org.

[UsamaSadiq]

Hi @robrap

• I'll make sure to keep the status updated on the issue.
• This was moved to blocked when I had to prioritize team coordination and management of Devstack work streams (Dockerfiles deprecation && devstack.py config migration) in absence of Soban but will be picked up again soon.

[robrap]

Thanks @UsamaSadiq. This missed the deadline of 2024-11-09. Our team discussed using Slack to give a 1 month warning that a DEPR deadline is approaching. However, maybe during a retro your team could discuss how to ensure that a deadline gets associated with the tickets so it stays top of mind. Thanks again.

[UsamaSadiq]

All the occurrences of paver have been removed from edX organization. Only change left is in the commerce-coordinator-private repo which has been shared with owning team for review but it is not a blocker for us any more.