Project

Profile

Help

Actions
Send by e-mail Copy link

Story #3777

closed

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

Added by amacdona@redhat.com almost 5 years ago. Updated over 2 years ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Easy Fix, Plugin Template
Sprint:
Quarter:

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).

Actions
Copy link
 #1

Updated by amacdona@redhat.com almost 5 years ago

  • Sprint Candidate changed from Yes to No
Actions
Copy link
 #2

Updated by bmbouter almost 4 years ago

  • Tags deleted (Pulp 3)
Actions
Copy link
 #3

Updated by bmbouter almost 4 years ago

  • Tags Plugin Template added
Actions
Copy link
 #4

Updated by bmbouter almost 4 years 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.

Actions
Copy link
 #5

Updated by daviddavis over 2 years ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF