Upgrading to 3.11 needs downtime but the changelog doesn't say so

Open Beginner friendly
#1,558 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
documentation

Research direction

Read the 3.11.0 changelog and compare its upgrade notes with the zero-downtime upgrade requirements linked in the issue. Add a note that upgrading requires downtime because migrations 0041 and 0042 add NOT NULL columns; done when the changelog clearly warns users before upgrading.

Written by the indexing model from the issue text.

Description

pulp_deb 3.11.0 adds migrations 0041 and 0042, which make new columns NOT NULL. Any 3.10 code still running during the upgrade then fails to upload debs or publish apt repos.

This doesn't follow the zero-downtime upgrade requirements. I think just a changelog note saying this release needs downtime would be good enough.

Dominant language
Python
Stars
73
Forks
94
Avg merge
4d 21h
Merged PRs (30d)
8

Getting set up

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 pulp/pulp_deb

All issues in pulp/pulp_deb

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.