summary page for process workflow?

[Jonathan Gibbons]

Iris,

What I sent was a work in progress of things that have tripped me up one 
way or another,
and that I've found it useful to make notes about. Think of it as one 
person's real world
checklist.  I'm more than happy for you to use it as a basis for a more 
general purpose
checklist. :-)

The bold numbered headings on the changePlanning.html page also provide 
a good
basis for a checklist.  If you took those headings, added a quick hint 
to each one
for the commands or websites involved, with links to the full page of 
details, then
you'd have something pretty good, I think?

-- Jon


iris clark wrote:
> Hi, Jon.
>
>   
>> 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
> missing.
>
> Perhaps I should enhanced the present set of steps on this page to
> contain a few key shell commands and references to appropriate tools:
>
>   http://openjdk.java.net/guide/changePlanning.html
>
> Then provide a condensed version of those steps?
>
> iris
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/guide-discuss/attachments/20080306/539d708c/attachment.html