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

Bug 379467

Summary: [pmi] Revision information should be maintained for all changes
Product: Community Reporter: Wayne Beaton <wayne.beaton>
Component: Project Management & PortalAssignee: Christopher Guindon <chris.guindon>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: chris.guindon
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: iOS   
Whiteboard: stalebug

Description Wayne Beaton CLA 2012-05-14 16:26:18 EDT 
Every time any node changes, we need to track what happened, who made the change, and when. I believe that Drupal's build-in revision management can help here and that it's a simple matter of implementing hook_node_save.

Note that Elections already explicitly set the revision information; we need to decide to either abandon this, or sort out how to augment it (i.e. don't overwrite revision comments if they already exist).
Comment 1 Eclipse Genie CLA 2014-05-19 19:38:20 EDT 
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 2016-08-10 12:52:40 EDT 
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 2018-08-01 18:27:27 EDT 
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 Eclipse Genie CLA 2021-09-13 14:00:03 EDT 
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 5 Wayne Beaton CLA 2021-09-13 14:47:52 EDT 
While I still think that this would be very useful to have, it's not something worth investing scarce development time and energy in.