On 27.12.2008, at 23:28, Alexander Limi wrote:
On Sat, 27 Dec 2008 09:56:23 -0800, Ross Patterson
<[email protected]> wrote:
One way to keep these cross-checks lightweight might be to start
with a
statement of impact. There are code changes, for example, that
have no
UI impact. In such cases, it would be fast and more painless if a
PLIP
champion noted this. Someone from the UI team could then corroborate
that the PLIP entails no UI impact and that would be the end of
it. If
there is an impact, then the PLIP champion would need to include
full UI
consideration for the impact in the PLIP. The UI team could then
review
both the statement of impact for accuracy and the UI consideration
for
sufficiency and completeness. The same would largely be true for the
doc team with the exception that, IMO, all changes have a
documentation
impact even if it's only for developers and so there should be no
option
to declare no impact.
This sounds like a good starting point. +1.
+1
i particularly like the notion of using workflow states as 'reminders'
to make sure aspects aren't missed.
cheers,
tom
--
Alexander Limi ยท http://limi.net
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
