I know that the way we have it today for tracking progress in the doc is far
from optimal but JIRAs may not be the easiest way either.
If we use JIRA for the doc, this is what I think the author should do:
- create a JIRA for documentation
- JIRA summary should match cwiki page title
- what priority should be used?
- specify affected releases
- assign the issue to itself
- add a link in the JIRA to the cwiki HTML page
- non English versions of the doc should also contain a link to the original
doc (dependency?)
- add a link to JIRA from the cwiki documentation page
- develop the actual documentation content and necessary samples
- no further status update/changes on the JIRA would be necessary while the
content is developed in cwiki
- close the JIRA once the document is finished
hmmm, on second thought, this may not bee too hard to deal with as long as we
keep the main focus in the doc and not in maintaining those doc JIRAs.
Let's give it a try for the remaining of the v1.1 and v1.1.1 doc, if it works
we could go full steam ahead for the next G release.
Comments?
Cheers!
Hernan
Jacek Laskowski wrote:
On 9/22/06, Lasantha Ranaweera <[EMAIL PROTECTED]> wrote:
I saw there is an empty sample application under web services section in
Geronimo user guide. Does anybody working on that? I would like to
contribute on that.
Once you've decided you'd go for it, could you please add your name to
the section so it's clear you're working on it? Or better yet, create
a jira issue and assign it to you. This way when we cut a release and
create RELEASE NOTES it will be noted. People will surely appreciate
it, i.e. your example and the way it's announced ;-)
BTW, please don't cross-post dev and user. It's an issue for the user
mailing list (but I must admit I would not have picked it up so early
if it'd been sent to user ;-))
Jacek
