Actions
Task #2762
closedPlanning: Transitioning from Pulp2 to Pulp3
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.
Updated by bizhang over 7 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bizhang
Updated by jortel@redhat.com about 7 years ago
- Sprint/Milestone changed from 43 to 44
Updated by bizhang about 7 years ago
- Status changed from ASSIGNED to CLOSED - COMPLETE
Results from the survey: http://pulpproject.org/2017/08/08/community-survey-results/
rchan was given a copy of the responses and will take it into consideration for the future pulp roadmap
Actions