[Pulp-dev] Sprint 47 Planning Minutes
Robin Chan
rchan at redhat.com
Fri Jan 4 20:35:29 UTC 2019
Sprint planning was held today and here are the meeting minutes. We had a
suggestion that we should share this information as it may be helpful.
A query for Pulp 3 Core RC blockers has been added to [1] and any
interested parties are invited to review and provide feedback (any items
missing or not needing to block the RC.)
Also, some of us learned what a cloud chamber [2] is and what to do with
leftover dry ice from the next Omaha steak delivery.
*04-Jan-2019*
*Action Items from last Sprint Planning*
- daviddavis: RPM team will plan some RPM distibution/kickstart trees
this sprint (add AI)
- Planning - goal to have stories by next sprint - migration and tagged
with proper Pulp 3 tags (check with Tanya when back)
- dalley: paperwork to ensure work not lost
https://pulp.plan.io/issues/3812
- dalley: https://pulp.plan.io/issues/4023
- austin: compile docs issues to discuss with docs team (add AI)
- create new story to move devel env (dkliban):
https://pulp.plan.io/issues/4234
*Dates & Sprint Goals/Focus*
https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans
Sprint 48 planning:
47 Dates: Friday Jan 04, 2019 - Thursday 24-Jan-2019
48 Dates: Friday Jan 25, 2019 - Thursday 14-Feb-2019
Jan 25 (date for next planning is 1st day of devconf?)
- Team members attending Devconf will ensure any planning items are
delegated prior to mtg
Dates for FOSDEM & Configmgmt Camp:
FOSDEM Feb 2-3
CfgMgmt Feb 4-6
*Other things happening during the sprint (including outages)*
- Pulp 2.19 - depsolving issue 3740 grooming
- Prep for devconf/FOSDEM/Cfgmgmt camp
- Task moving unit tests Pulp 2 over to new OpenStack
- RH staff PTO specifics redacted
*Current sprint:*
Anything not moving forward?
https://pulp.plan.io/issues?query_id=1
<https://pulp.plan.io/issues?query_id=112>12
<https://pulp.plan.io/issues?query_id=112>
keep sat 6.5 items on sprint 4253, 4252, 4268
4189 - unsure if done during next sprint. build team staff can do as time
allows.
4066 - on hold, won't move to new sprint
4263 - won't move to new sprint
*Sprint candidates:*
https://pulp.plan.io/issues?query_id=26
4132 - not added, if Dana will note and add to sprint if no other
appropriate tasks left on sprint (low priority)
*Pending Items or Stakeholder concerns:*
- Features that are in planning and anticipated to be ready to add
before end of sprint.
- add lazy sync feature - will discuss with Jeff - pass through cache
(or maybe next sprint)
- 4294 - design discussion
- namespacing endpoints https://pulp.plan.io/issues/4279
*QE Focus:*
* Pulp3 High Priority Test Tickets
* OpenStack migration (to PSI Openstack)
*Action Items:*
- rchan: new, assigned, post - move Monday morning
- rchan: Clear Sprint Candidate https://pulp.plan.io/issues?query_id=26
- daviddavis: RPM team will plan some RPM distibution/kickstart trees
this sprint
- austin: discuss compiled docs issues to with docs team
- rchan send note to pulp-dev mtg minutes
- bmbouter - put together rc strategy etherpad to collaborate on
communication about Pulp 3 RC
[1] https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans
[2] https://youtu.be/xky3f1aSkB8
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190104/dcdf90ae/attachment.htm>
More information about the Pulp-dev
mailing list