WS-CAF issues list is open

As promised yesterday, we've managed to get the bugzilla server up and
running to maintain the WS-CAF issues. I've populated it with all of the
issues in the published errata and a few that were sent to me since then.
Apologies if there are missing issues that people sent me. I also haven't
added any issues from the face-to-face.

In order to add or examine an issue, you need to go to:
http://services.arjuna.com/wscaf-issues/

First you should create an account for yourself, which will be used to track
issues you submit or update. I would imagine that we'd use this information
to select initial "champions" for issues too. Once you've got an account
(which takes seconds), you can either query the current issues, or submit a
new issue.

Let's suppose you want to query. You can get a summary of all issues via the
"Get summary reports" link. Here you get a coarse grained approach to the
issues, which is basically by specification and "engineer" (bugzilla's term,
not mine) - the person who is in charge of that issue. By clicking on the
issue hyperlinks you can then go to each specific issue and see what it
describes. You then have the ability to add comments. *Don't* close the
issue. For fairly obvious reasons an issue will only be closed when the
committee votes on it, and as issues editor I suppose I'll be the person
closing them.

If you query via the "Query existing bug reports" you get much finer grained
control over what issues you want to see. Ignore the Hardware/OS fields -
this is bugzilla showing its roots. As you'll see, you can search over
entire specifications or just within certain components of those
specifications. The Product/Component separation is as we agreed last year
and is in the minutes, so I won't go over it again.

Now when you want to add an issue you first have to select the Product
(specification). Selecting the right link brings up another page where you
get to select the component. You *must* select a component for your issue.
If you think there is no relevant component, then let me/the group know and
we can always add another one once we've agreed. If you want to change the
Platform/OS field then I'd suggest all/all

You can select the severity of the issue, but if you're not sure we can
always change that later once we're agreed. Leave the "Assigned To" field
blank, then just fill in the Summary and Description fields and that's all
there is to it. When the sendmail issue is fixed, notifications on all new
issues and updates to existing issues will be sent to the group
automatically. All emails will be sent as though coming from me, though as I
said above, each issue internally will have the actual submitter id.

When we get into the process properly, bugzilla allows us to track
dependencies between issues, which you'll see as soon as you enter an issue.

For completeness, I've also attached the current list of issues as they
appear in
bugzilla.

Mark.

----
Mark Little,
Chief Architect, Transactions,
Arjuna Technologies Ltd.

www.arjuna.com