summary page for process workflow?
iris at sun.com
Thu Mar 6 16:48:29 PST 2008
> For my part, a quick reference guide is useful, more details than a
> flow chart, but less detailed than multiple pages of info. I've been
> developing one for myself and other compiler folk. Having it be
> hyperlinked into more detailed pages would be good. I'll attach the
> one I've been using for myself, as an example. Obviously, this one is
> specific to the compiler team, but you get the idea.
Thanks for the sample. I like it, though I'd argue about the content.
For instance, you list approvals after review when in fact, some
people might argue that some approvals need to be started before the
code is finalized for review. Also, several bug database updates are
Perhaps I should enhanced the present set of steps on this page to
contain a few key shell commands and references to appropriate tools:
Then provide a condensed version of those steps?
More information about the guide-discuss