Story #1305
closedRemove pre Pulp 2.4.0 migrations and require users are upgraded to 2.4.0 before upgrading to 2.8.0
100%
Description
We have a lot of migrations and they are becoming difficult to maintain as they require portions of the codebase to never change. Of course the codebase changes regularly so we do a lot of work to maintain the ability for users to upgrade from any version to any version.
We are considering requiring users to upgrade to at least 2.4.0 before upgrading to a version of 2.8.0+. We can delete the pre-2.4.0 migrations from platform and all the plugins. See the checklist below for more details on the deliverables.
Updated by bmbouter over 8 years ago
- Subject changed from Remove pre Pulp 2.5.0 migrations and require users are upgraded to 2.5.0 before upgrading to 2.8.0 to Remove pre Pulp 2.4.0 migrations and require users are upgraded to 2.4.0 before upgrading to 2.8.0
- Description updated (diff)
mhrivnak wrote:
Yes please.
Done. It now reflects 2.4.0 instead of 2.5.0. If the story has enough detail, the next step is to mark it as 'Groomed'.
Updated by mhrivnak over 8 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to mhrivnak
Updated by mhrivnak over 8 years ago
- % Done changed from 0 to 70
- Groomed changed from No to Yes
Added by mhrivnak over 8 years ago
Added by mhrivnak over 8 years ago
Revision ea527684 | View on GitHub
Removing migrations from prior to 2.4.0.
Changing the rules to allow gaps in migration numbers, and to fast-forward brand new migration trackers instead of applying migrations to empty collections.
re #1305
Updated by mhrivnak over 8 years ago
pulp_puppet had no migrations prior to 2.4.0, so there is nothing to do for that plugin.
Added by mhrivnak about 8 years ago
Updated by mhrivnak about 8 years ago
- Status changed from ASSIGNED to POST
- % Done changed from 70 to 100
Updated by mhrivnak about 8 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp_rpm:a2b541b9a9184a679f1331d35a0383eab5d1308b.
Updated by dkliban@redhat.com about 8 years ago
- Status changed from MODIFIED to 5
Updated by dkliban@redhat.com almost 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Removing migrations from prior to 2.4.0.
Changing the rules to allow gaps in migration numbers, and to fast-forward brand new migration trackers instead of applying migrations to empty collections.
re #1305