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

Bug 402190

Summary: [pmi] Allow Planning Council chair (and others) to modify simultaneous release participants
Product: Community Reporter: Wayne Beaton <wayne.beaton>
Component: Project Management & PortalAssignee: Eric Poirier <eric.poirier>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: chris.guindon, david_williams
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Wayne Beaton CLA 2013-03-01 16:49:16 EST 
This functionality is currently restricted to system administrators.

The previous implementation let individual project leads and committers add themselves to any release at any time (including past releases). This was difficult to track and resulted, I believe, in a few projects sneaking in.

Since management of the simultaneous release is within the duties of the Planning Council, it makes sense to me to grant them the ability to modify the records.

So... Just the Planning Council chair, or any member?

Is this something that we should let the PMC do? (I think "no", but thought that I'd float the idea)
Comment 1 Eclipse Genie CLA 2015-02-20 16:45:20 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2017-02-10 01:22:29 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2019-02-03 18:27:05 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eric Poirier CLA 2019-07-17 11:31:42 EDT 
Hi Wayne,

Does this still needs to be implemented in the current version of the PMI?

Thanks.
Comment 5 Wayne Beaton CLA 2019-07-17 11:52:30 EDT 
We need something like this, but I'm not sure if the solution that I've proposed is the right one (at least not any more). Let's mark this as WONTFIX, and I'll work with the Planning Council to sort out what we actually need/want.