Project

Profile

Help

Task #2762

closed

Planning: Transitioning from Pulp2 to Pulp3

Added by pcreech almost 7 years ago. Updated about 5 years ago.

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

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 25
Quarter:

Description

As an area critical to the success of Pulp3, we need a system for the successful transition from pulp2 to pulp3 for various stakeholders. To do this, some questions will need to be answered from our various stakeholders (Community, Satellite, RCM, etc...):

What are the expected migration use cases?

What concerns are there around the transition? Topics include:

  • Deployment logistics
  • API use
  • UI use
  • notification use
  • Dropped features
  • Data migration
  • Downtime

How can we ease those concerns?

Once these questions are answered, stories and tasks will need to be created for the various next steps.

Also available in: Atom PDF