-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GH Request] Fork pinax-requirements in openedx org #911
Comments
Thank you for your report! @openedx/axim-oncall will triage within a business day. Simple requests usually take 2-3 business days to resolve; more complex requests could take longer. |
Can do @iamsobanjaved . Before I fork, can I confirm that Arbi-BOM is OK with being listed as maintainer of the forked repo? |
Yes you can list us as maintainer |
Fork created here: https://github.com/openedx/pinax-announcements Arbi-BOM is added with Maintain-level access. Keeping this ticket open for now because I need to do a couple small things to make sure that Arbi-BOM are set up as maintainers. |
In review: openedx-unsupported/pinax-announcements#2 |
catalog-info.yaml is merged, and I messaged #maintainer-pilot to let them know that Arbi-BOM will be maintaining the fork. |
Firm Name
2U
Urgency
High (< 3 days)
Problem/Request
Kindly fork pinax-announcements in openedx org.
Reasoning
We are nearing the Quince branch cut, and want to give the Django 4.2 upgrade in the Quince release. This package pinax-announcements is giving errors on Django 4.2 so kindly fork this package so we can add support for Django 4.2 in our fork and then once support arrives upstream, we can close our fork.
Choosing high priority just because the branch cut is approaching.
The text was updated successfully, but these errors were encountered: