Skip to content

docs: note removal of built-in XBlocks in Willow dev/op notes - #1554

Draft
irfanuddinahmad wants to merge 1 commit into
openedx:mainfrom
irfanuddinahmad:irfanuddinahmad/willow-remove-builtin-xblocks
Draft

irfanuddinahmad wants to merge 1 commit into
openedx:mainfrom
irfanuddinahmad:irfanuddinahmad/willow-remove-builtin-xblocks

Conversation

@irfanuddinahmad

Copy link
Copy Markdown
Contributor

Summary

Adds one Deprecations & Removals entry to the Willow dev/op release notes: the built-in XBlock implementations are removed from openedx-platform. The Verawood notes announced this removal for Willow.

One entry covers all 8 blocks (Annotatable, Discussion, HTML, LTI, Poll, Problem, Video, Word Cloud). It also covers the removed USE_EXTRACTED_*_BLOCK settings, the unchanged xblock.v1 entry point names, and the import change for custom code.

Requested by @farhan in review of openedx/openedx-platform#38745.

Related platform PRs (epic openedx/openedx-platform#37819)

openedx/openedx-platform#38744 (Poll), #38745 (Word Cloud), #38746 (Annotatable), #38747 (LTI), #38748 (HTML), #38749 (Discussion), #38750 (Video), #38751 (Problem).

None of these PRs is merged yet. I'd keep this PR open until they land, or until we confirm that all 8 will be in Willow. If a block misses the release, I'll drop it from the list.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Nov 19, 2026
@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @irfanuddinahmad!

This repository is currently maintained by @openedx/wg-maintenance-docs.openedx.org.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.


Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants