Patchwork 3.0 migrations are suboptimal

Open
#420 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
database

Research direction

Start with the linked July 2021 mailing-list report, which describes the migration-efficiency issues when moving from Patchwork 2.2 to 3.0. Then locate the migration entry points in the Patchwork codebase and identify the specific improvements covered by this catch-all issue; done means those migrations are more efficient and their behavior is verified by the relevant tests.

Written by the indexing model from the issue text.

Description

bug

As reported on the mailing list, there are a couple of things we can do to improve the efficiency of migrations when moving from Patchwork 2.2 to 3.0. This is a catch-all bug to track these improvements.

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.