[Framework-Team] Re: PLIP lifecycle

Tres Seaver tseaver at palladion.com
Fri Jan 2 19:33:32 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Erik Rose wrote:
> On Dec 28, 2008, at 5:23 , Tom Lazar wrote:
> 
>> i particularly like the notion of using workflow states as  
>> 'reminders' to make sure aspects aren't missed.
> 
> OTOH, workflow states are serial, and it'd be a shame to force teams  
> to do their evaluations in a specific order.

You can actually have multiple workflows for a given type.  I may be the
only person who has ever actually used the feature, but it is truly
helpful at times.

Having the doc team work in one (simple) workflow, the UI team in
another, and the FWT in the "main" workflow, with gates based on the
other two, might be the best solution.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJXmwM+gerLs4ltQ4RAo4wAKCh9iooip7l2tmaH7n76VQ0blD7wgCgw/ec
CZdooBBPBwtS4csaAXmLYoY=
=0vbS
-----END PGP SIGNATURE-----





More information about the Framework-Team mailing list