Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312716 - Add rows to Simultaneous Release Compliance Grid for IP Log and Docuware
Summary: Add rows to Simultaneous Release Compliance Grid for IP Log and Docuware
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Project Management & Portal (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Portal Bugzilla Dummy Inbox CLA
QA Contact:
URL: http://eclipse.org/helios/planning/Si...
Whiteboard:
Keywords:
: 311921 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-12 17:05 EDT by Wayne Beaton CLA
Modified: 2010-05-27 11:26 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Beaton CLA 2010-05-12 17:05:56 EDT
We are tracking this information using the standard mechanism we use for all project releases. Each project participating in the release train will have  release record that will include links to the approved ip log and docuware once we receive this. We should be able to use this information to populate a row in the table to make it easy to quickly determine which projects need to still provide this information.
Comment 1 Anne Jacko CLA 2010-05-19 15:01:32 EDT
Wayne, this may be overkill, but there are really two states for the IP Logs and the docuware -- submitted and approved. Ideally the update to the grid would show both states for each item, but not sure if that's easily done from the data you can pull from the Portal record.

For the IP Log, it's easy to tell these two states. There's a field that says "Legal Review Requested" that indicates submission. Then when the log is approved, the IP Log URL field and the IP Log Posted field are filled in, indicating approval.

For the docuware, it's kinda tricky. Normally the fields for Slides URL and Slides Posted are filled in only after the docuware has been finalized and uploaded. For Helios, I've been completing the Slides Posted field when they are first sent to us, because I don't see any other way to indicate that they've been submitted. Then when the docuware is finalized, I'll upload them and fill in the Slides URL field to indicate approval.

I'm hoping you can get the grid updated soon -- it would be really useful to me right now -- especially since I plan to nag the projects who haven't sent in their materials early next week. Without the grid, to check the status I have to check the Helios review entries for the individual projects. This is a PITA, since I have to look at the entire list of previous reviews (which is in alphabetical order) and find the one I want, click on it, look at it, then go back. And repeat...

Of course I can always look at emails to figure out the status, but that's just as much as PITA, if not more.
Comment 2 Wayne Beaton CLA 2010-05-27 09:35:33 EDT
Two new rows have been added to the Compliance Grid as requested. Green means that the corresponding item has been received and has been approved. Light-green means that we've received it, but haven't processed it yet. Red means that we know we haven't received it yet. Yellow means we don't know.

For completeness I'll include some explanation about the implementation...

Due to some restrictions on database access, this script cannot connect to the Foundation database to get the IP Log and Release Documentation information. Instead, we have to connect via Ajax call from the browser and do a little JavaScript magic. The first thing we do is create a couple of extra rows in the table with placeholders for the real information. We later do an Ajax call to /projects/xml/review_status.php to retrieve XML data about the reviews; that data is then parsed and used to properly populate the two rows. Painful? Yes. 

I'm marking this bug as fixed. Reopen if I've missed anything.
Comment 3 Wayne Beaton CLA 2010-05-27 11:26:52 EDT
*** Bug 311921 has been marked as a duplicate of this bug. ***