Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 280952

Summary:	[pmi] IP Log Metadata
Product:	Community	Reporter:	Gabe O'Brien <gabe.obrien>
Component:	Project Management & Portal	Assignee:	Portal Bugzilla Dummy Inbox <portal-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Gabe O'Brien

2009-06-19 16:30:12 EDT

Currently the IP Log Metadata allows projects to enter multiple IP logs, but there is now way to differentiate the logs.  This enhancement would allow projects to 'tag' an IP log as being for a specific release.

This IP log information could then be mined and displayed on the standard project page for each project.  This information could be very helpful to companies and individuals wanting to adopt a project for their own use.

Comment 1 Wayne Beaton

2012-04-02 22:42:45 EDT

I would like to move the IP Logs directly into the Project Management Infrastructure at some point. The current work around is to attach the Approved IP Log directly to the release record. This is supported in both the Developer Portal and the new Project Management Infrastructure.

Comment 2 Wayne Beaton

2012-05-08 13:30:19 EDT

We currently capture the generation information with a project. Currently, this amounts to a Bugzilla product/component and a list of source repositories.

Recent discussions on the rt-pmc mailing list regarding the release of subsets of project code suggest that we should provide the ability to specify the generation information on a per-release basis. The Jetty project, for example, might specify--as part of the release record--that only bugs tagged in a certain way are part of the Jetty "8.0" release, but not the "7.0" release (which will have separate release records). 

It might be enough to specify that some subset of the project's repositories include code that is contained in the release (this would work in the case of Virgo releasing runtime and tools separately). But in Jetty's case, we might have to specify a tag to limit the parts of the repository that we investigate when generating the log.

I can see this manifesting as a "tentative" log in the release record until a project member opts to freeze the log. At that point, the log is generated and sent to the IP team for review.

Comment 3 Wayne Beaton

2014-08-20 16:45:47 EDT

The PMI lets us attach an IP Log to a specific release record. I think that this solves the problem.