I start from a position of trusting committers to do the right
thing.
The problem with enforcement is that there are always corner cases
that cause everybody grief. I'd rather trust the committers to do
the right thing. This, along with revision management should get us
there.
Another thing that I'd like to add to the PMI is the ability to
subscribe to changes on any individual record. We could also
entertain automatic notification to the PL or all committers
whenever a record is changed. I generally don't like sending too
many emails, so we'll have to figure out how to strike a balance.
Wayne
On 03/15/2013 02:48 PM, Ed Willink
wrote:
Hi Wayne
The PMI is built on Drupal. Drupal is a content management
system.
There is a "Revision Information" tab at the bottom of the page
that you can use to create a new revision whenever you want.
I've been toying with the idea of creating a revision every time
the form is saved. Thoughts?
That could tip the balance.
For a project plan, what kind of freezing is in place? At present,
and under the new system presumably I can just go back to the
Helios plan and create a very different impression to users and
not what was endorsed by the Release Review. CM at least
demonstrates that I have done this.
Perhaps the RR submissions should be tagged, and only EMO/PMC are
able to move tags thereafter.
Regards
Ed Willink
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
