Plan

Add launch feedback to this thread.

I reviewed OSG certificates issued on the 4 MyProxy servers (warm, cool, tepid, and jackfruit) to see if any non-test certs had been issued after 2018-05-31. warm (the primary OSG MyProxy server) had the following certificates not generated by me as part of my monthly tests.

'Ensure that CSA owners have appropriate startup or developer allocation processes available.'  Based on the comment from Nancy and what the requirements for the correct solution turn out to be  this may be more than .2 effort but probably not more than a week.  Its hard to say from the lack of d

The Deliverables table seems to be messed up. The first column header is "Due by" but the data in the column doesn't appear to be due dates.

The due dates in the plan end in late 2018, but the "Fix version" is PY7 which ends in August 2018. Should the fix version be changed to PY8 if it isn't going to be finished until PY8?

The use cases describe the ability for SPs to publish their support of the CSA capability (SPI-07), and the ability for community software providers to identify which SPs support CSAs and the procedure to follow to use a specific SP's CSA (Step 2 in RC-03).

The Deliverables table seems to be missing one or more columns.  The headings are "Due by" and "Activity Deliverable", but there are no dates under "Due by."

The due dates in the plan are all in 2017.  I think they should be updated to be in the future rather than the past. 

Since this is marked for PY7 completion (ending in August 2018), I expected to find dates that showed completion by August 31, 2018.

Based on the OSG announcements, new certificates will not be issued from the OSG CA after 5/31/2018. Assuming a maximum expected certificate lifetime of 13 months, that puts the full retirement date at ~June 30 2019, until which we expect to be able to retrieve and verify current CRLs.

Looks good to me.