Please sign up before copying a ticket over! First column
Copy description and any major updates in the comments which aren’t yet included in the Jira description
Link back to the Jira issue
@Jeremy Bowman will work with Diana to add a new “Migrated” status or such to the Jira board for tickets that have moved over to GitHub Issues before completion.
Persistent grades - should this be made the default and remove the option of doing otherwise?
Feels appropriate for a DEPR ticket, removing the ability to have non-persistent grades
@Dave Ormsbee (Axim) will write this up
codejail CI is just about moved from Jenkins to GitHub Actions, should be able to make that Jenkins server private soon
DEPR blended project brief has been written, will move forward once Jeremy has time to review and Diana has time to nudge it along (both should happen relatively soon)
@Feanil Patel will review other feature flags that are currently off by default but really should be on by default (completion, etc.)
Should internal and external DEPR channels be joined?
The internal one has been very low traffic since the WG became public, may make more sense to archive instead. We’ll give it a little time to see if it gets usefully used for 2U-private code deprecation.
Github issue about deprecating it in public engineering (roadmap?)
Concerns brought up during a contributor’s meeting
Previously discussed with Sarina
Maybe we should put it through the proper DEPR process so we can formally abandon it if there’s enough pushback
There’s a separate possible option eox_tenant for multitenancy as a replacement - should get feedback from the rest of the community
Action item: move/create depr ticket and announce with a longer acceptance period to see if eox_tenant is a good replacement - follow up to see if we have a point person on this discussion, then let them take care of announcement.
@Michael Terry (Deactivated) async update: I have PRs to remove legacy outline & dates tabs, but since we’re so close to the Nutmeg cutoff, I’ll just wait until after then (April 11th) to land them, to let Open edX have another release with the legacy views still supported.
April 12, 2022
[Feanil] Comms improvement as things are going away(From core-contributors meetup)
Can we have more details in the deprecation section of the Release notes?
What are other things we can do to make the DEPR board easier to consume as a summary of work.
Take a look at what landed between releases
do lookups/create filter for the DEPR board for each release - what got removed between these two dates
create label ‘needs release notes’ for DEPR tickets
badger people until they’re added to the release notes
archive things at the Open edX release boundary
add agenda item for WG
@Feanil Patel talk to BTR about contacting DEPR after a new release has been cut in order to trigger our own process
@Diana Huang take ideas and turn into a checklist for next release
Working Group Meetup at Open edX Conference
Feanil will be our representative
Blended project update
Making progress through EdxRestApiClient
Starting on other tickets
Old Mongo progress
remove legacy outline and dates tabs
preview mode in studio still relies on the courseware endpoints and template rendering
TNL has a ticket for handling this case
site_configuration DEPR ticket still needs to be created
Flags that should maybe be enabled by default/flag should be removed.
[Request] Review the flags as a group and figure out which ones to DEPR
Process: Do we want a depr ticket for each of these? Should we batch them together?
Change defaults for the ones we believe should be a different default
Add something to the next release notes about the flip
1 DEPR for Studio login flow
1 DEPR for removing the ones that we want to remove
Removal will happen after Olive is cut.
Announcement in Discourse about turning these flags true
Also add to release notes for Olive that we are changing these defaults
a good place to discuss how to do this in the future and think about it as we catch up to the existing backlog
systems for handling backwards incompatible migrations
DEPR process questions
moving from proposed → communicated
no review steps in between
How can we tweak the incentives around deprecation?
on top of the existing discussions previously
talking to product owners and engineering managers
allocating time for deprecation work with maintenance
FC retro and RCA to discuss process improvements
general RCAs around deprecation projects to talk about things more holistically
how could this feature have been designed to make it easier to remove? etc.
several mini retros around different parts of the FC work
Agenda (18 October 2022)
Who is going to be responsible for it?
[Jeremy] How much do we really want/need to keep this at all? Simon did some discovery on this, and determined that http://edx.org LMS and Studio get pretty minimal benefit from Elasticsearch usage; other installations may use these features more.
@Dave Ormsbee (Axim) : See if tCRIL can fund some of this work.
While deprecating RateXBlock, it became apparent that we’re a little fuzzy on exactly what needs to happen before uninstalling an XBlock with non-zero production usage. We should figure this out and document it, for both http://edx.org usage and reference in Open edX release notes.
MIT is probably using some of the stuff in configuration, even if they aren’t using a lot of the Ansible code
Arbi-BOM has been migrating devstack containers off of using configuration
edxops docker hub will probably be shut down, openedx docker hub may be shut down since it only hosts devstack images currently, though it does also have the edx-platform github action runner images as well.