A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | AR # | Category | Prime | Release | Priority | Due | Forecast | AR | Comment | ||||||||||||||||||||
2 | 1 | General | Ghada | General | Low | Done | Done | Bill to set up a shared Google Drive for everything. | 1/24/2019 (bz): Ghada did this - it's at https://drive.google.com/drive/folders/1YlAlWT7FtSFNyYDdJ2hbFFW4aNGQXCHY 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
3 | 2 | Security | Ken | 2019.05 | Medium | Done | Done | Security team to state their plan/policy on current and back-port. | 2/25/2019 (bz): per Ken, policy is complete; plan provided on Community call: o Tool selection – Match 1st o Generate a Jenkins Job – March 22nd o Pilot on master – first report April 5th 2/13/2019 (bz): per Ken, they have a provisional policy now - will continue working to firm it up, then set the plan 1/30/2019 (bz): per Ken, they're working on a process/policy - they've got a skeleton in place now, working to make it systematic, quantified - forecast for next week's meeting 1/24/2019 (bz): gave the action to Ken - will ask him to flesh this out & set priority 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
4 | 3 | Security | Cesar | 2019.05 | Medium | Feb 6 | Intel to make their CVE methodology public. | 2/27/19: Security team has reviewed a set of scanning tools and posted a selection to the mailing list. Believe this can be closed. Bill to check with Brent. 2/13/2019 (bz): Cesar working with Victor - this will be on the agenda for the next Security meeting 1/30/2019 (bz): Brent requested Cesar to send details of the test methodology to the Community (*not* the actual results), Cesar agreed to do 1/24/2019 (bz): assigned to Cesar - Bruce will follow up with Cesar 1/21/2019 (bz): from mini-PTG | |||||||||||||||||||||
5 | 4 | Documentation | Bruce | 2019.05 | High | Feb 6 | Done | Doc team to create storyboards for the 3 areas that need documentation work. | 1/30/2019 (bz): part of Doc team's current thrust 1/24/2019 (bz): these will be created once the dust settles on the doc framework 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
6 | 5 | Documentation | Bruce | 2019.05 | High | Feb 6 | Done | Doc team to publish the framework of documentation they want to create. | 1/30/2019 (bz): part of Doc team's current thrust 1/24/2019 (bz): Bruce has published a draft of this, it's in progress 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
7 | 6 | S/W Management | Saul | 2019.05 | Medium | Done | Done | Brent, Saul, Dean and the interested cores to sort out the issue around the TiS numbering issue. | 1/24/2019 (bz): consider this done 1/21/2019 (bz): I think the email Saul sent since the mini-PTG covers this off - Saul to confirm. 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
8 | 7 | Distro Non-OpenStack | Cindy & Ghada | 2019.05 | High | Done | Done | Cindy & Ghada to state the plan for getting the Mellanox driver fix in. | 1/30/2019 (bz): closed, they have a plan - see "OVS/DPDK upgrade status" in https://etherpad.openstack.org/p/stx-status 1/24/2019 (bz): Bill to check with Ghada re: how soon they think they can have a plan for this 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
9 | 8 | Test: Unit Test | Bruce | 2019.05 | Medium | Bruce to provide an update about how the Intel team can contribute to the Unit Test effort. | 3/6/2019: Currently this is below the cut line for Intel :( 1/30/2019 (bz): no update 1/24/2019 (bz): Bruce to discuss internally 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||||
10 | 9 | Test: Unit Test | Bill | 2019.05 | High | Jan 30 | Team to identify which domains/repos need short term focus for unit tests. | 1/30/2019 (bz): no update 1/24/2019 (bz): Bill to provide input on this from WR perspective 1/21/2019 (bz): from mini-PTG | |||||||||||||||||||||
11 | 10 | Test: Feature Test | Ada | 2019.05 | Medium | Done | Done | Post feature test template to Wiki. | 02/05/2019 (ac): https://wiki.openstack.org/wiki/StarlingX/TestCaseDocument 1/30/2019 (bz): in progress, Ada will have it posted this week 1/24/2019 (bz): Ada to post the feature test template to the wiki (Numan sent it) 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
12 | 11 | Documentation | Bruce | 2019.05 | High | Create a developer guide for StarlingX developers - need to define what should be in it first. | 1/30/2019 (bz): part of Doc team's current thrust 1/24/2019 (bz): this is part of the overall documentation framework that Bruce & the doc team are working on (#5) 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||||
13 | 12 | Build | Ken | 2019.05 | High | TBD | Apr 12 | Confirm w/ CENGN about the plan for daily automated sanity – are they ok with this, resource-wise. | 2/25/2019 (bz): per Ken, not planning to start this action item until after April 5th (set forecast to April 12) 2/13/2019 (bz): in progress with Ken 1/30/2019 (bz): we discussed that this is part of a more general question about resources (including HW) needed for regular maintenance activities like this - we need to flesh this out and share with CENGN, and also consider the possibility of not just using CENGN's services/resources for this 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
14 | 13 | Test: Strategy | Ada & Numan | 2019.05 | High | Done | Done | Add the test strategy “next steps” into the Release Plan – prioritize, populate dates. | 2/25/2019 (ac): done 02/05/2019 (ac): WIP - to be done 02/08 1/30/2019 (bz): Test team working to add dates to their deliverables in the Release plan 1/24/2019 (bz): items have been added to the release plan, but all but one have no dates - what is the plan for getting dates against the other items? 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||
15 | 14 | Test: Performance Test | Ada | 2019.05 | Medium | Check OPNFV's performance test suite - what can we learn/use from that? | 2/13/2019 (bz): per Ada, we will use OPNFV's metrics; the set of metrics to be defined by end of next week, first set published by mid-March 2/05/2019 (ac): tools/other projects explorations to be covered as part of the spec (row 15). Let's follow up on that task. 1/30/2019 (bz): this will be part of Victor's performance test document - Ada to provide a forecast 1/24/2019 (bz): Ada to provide update 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||||
16 | 15 | Test: Performance Test | Victor | 2019.05 | Medium | Publish a spec for which metrics will be covered by performance tests. | 2/13/2019 (bz): see #14 2/05/2019 (ac): To be done 02/08 1/30/2019 (bz): Ada to provide a forecast 1/24/2019 (bz): Victor has published a working document to collect input/requirements for Performance Testing 1/21/2019 (bz): from mini-PTG | ||||||||||||||||||||||
17 | 16 | Future Release Candidates | TSC | 2019.11 | Medium | Prioritize the various items that are part of the “VM/Container” theme. | 1/21/2019 (bz): from mini-PTG - TSC to sort this out in 2019.11 time frame | ||||||||||||||||||||||
18 | 17 | Future Release Candidates | TSC | 2019.11 | Medium | Sort out the plan for Multi-Tenancy. | 1/21/2019 (bz): from mini-PTG - TSC to sort this out in 2019.11 time frame | ||||||||||||||||||||||
19 | |||||||||||||||||||||||||||||
20 | |||||||||||||||||||||||||||||
21 | |||||||||||||||||||||||||||||
22 | |||||||||||||||||||||||||||||
23 | |||||||||||||||||||||||||||||
24 | |||||||||||||||||||||||||||||
25 | |||||||||||||||||||||||||||||
26 | |||||||||||||||||||||||||||||
27 | |||||||||||||||||||||||||||||
28 | |||||||||||||||||||||||||||||
29 | |||||||||||||||||||||||||||||
30 | |||||||||||||||||||||||||||||
31 | |||||||||||||||||||||||||||||
32 | |||||||||||||||||||||||||||||
33 | |||||||||||||||||||||||||||||
34 | |||||||||||||||||||||||||||||
35 | |||||||||||||||||||||||||||||
36 | |||||||||||||||||||||||||||||
37 | |||||||||||||||||||||||||||||
38 | |||||||||||||||||||||||||||||
39 | |||||||||||||||||||||||||||||
40 | |||||||||||||||||||||||||||||
41 | |||||||||||||||||||||||||||||
42 | |||||||||||||||||||||||||||||
43 | |||||||||||||||||||||||||||||
44 | |||||||||||||||||||||||||||||
45 | |||||||||||||||||||||||||||||
46 | |||||||||||||||||||||||||||||
47 | |||||||||||||||||||||||||||||
48 | |||||||||||||||||||||||||||||
49 | |||||||||||||||||||||||||||||
50 | |||||||||||||||||||||||||||||
51 | |||||||||||||||||||||||||||||
52 | |||||||||||||||||||||||||||||
53 | |||||||||||||||||||||||||||||
54 | |||||||||||||||||||||||||||||
55 | |||||||||||||||||||||||||||||
56 | |||||||||||||||||||||||||||||
57 | |||||||||||||||||||||||||||||
58 | |||||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||||
100 |