OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: JIRA Work Flow Proposal, was Re: [office] All done

To get an understanding what the work flow in JIRA for these issues
could be now, I've started to add the comments and proposed resolution
that I have forwarded as documents previously to the items. I have
entered the proposed resolutions into the "proposal" field. To be able
to differ between those item where we have a proposed resolution and
those where we have none, I've set the status of those items where we
have a proposed resolution to "Resolved". This is the 3rd status in the
chain "New" -> "Open" -> "Resolved" -> "Applied" -> "Closed".

My proposal how we proceed is:

Whoever has time and and interest may comment on an item, and may
provide a resolution. This resolution is recorded in the "proposal"
field. If a proposal for a resolution does exist, the proposer of the
resolution sets the status of the issue to "resolved".

Patrick (or myself if an issue affects the schema) takes the issues
whose status is "resolved" and applies the proposed resolution to the
specification text. He then sets the status to "Applied".

The changes to the specification still will be recorded. We continue to
have a week for TC internal reviews of drafts before we vote on them in
a TC meeting, or we conduct electronic ballots for committee drafts, 
that run at least a week anyway, so that there is the same time 
available for a review.

TC members therefore have the choice to either watch the items in JIRA,
or to just review the changes in the next draft. The approval of a
resolution takes place with the approval of a committee draft. This
means that nothing that we do in JIRA implies any kind of approval by
the TC, and that it is not required to watch the changes in JIRA to
figure out what changes are made in a draft.

When a draft has been approved as committee draft, all issues applied to
that draft are closed (unless someone has objected to a particular

I have created two new filters:

"Open 1.2 Editorial Notes" lists those items whose title starts with
"Editorial Notes" and that are open. This filter may be used to find all
issues for which no resolution does exist yet.

"Resolved, unapplied 1.2 Editorial Notes" lists those items for which a
resolution has been proposed, and whose status is "resolved". This
filter is useful if you want to review proposed resolution, but also
useful for Patrick to find the items that may be ready to be applied to 
the specification.

Best regards


On 05/28/09 20:05, robert_weir@us.ibm.com wrote:
> You probably want to delete all of those 260+ notifications from JIRA. 
> These was a one-time port of Patrick's remaining editor notes. They've 
> been entered, opened, and assigned to Patrick.  This will make it easier 
> to track these items going forward.
> Regards,
> -Rob
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

Michael Brauer, Technical Architect Software Engineering
Sun Microsystems GmbH             Nagelsweg 55
D-20097 Hamburg, Germany          michael.brauer@sun.com
http://sun.com/staroffice         +49 40 23646 500

Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
	   D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]