Project

Profile

Help

Story #3777

As a plugin writer, I am instructed how to handle migrations

Added by amacdona@redhat.com over 1 year ago. Updated 6 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Easy Fix, Plugin Template
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

For development, we recommend keeping the migrations out of the git repository by adding them to the .gitignore.

When the model layer has stabilized, the migrations should be committed (and removed from the .gitignore).

History

#1 Updated by amacdona@redhat.com over 1 year ago

  • Sprint Candidate changed from Yes to No

#2 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

#3 Updated by bmbouter 6 months ago

  • Tags Plugin Template added

#4 Updated by bmbouter 6 months ago

  • Project changed from 27 to Pulp

The plugin template Redmine project is being consolidated into the Pulp Redmine project so all issues are being moved over.

Please register to edit this issue

Also available in: Atom PDF