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: Re: [office] office-comment -> JIRA migration

On 05/13/09 09:30, Peter Junge wrote:
> Rob,
> robert_weir@us.ibm.com wrote:
>> The important thing, I think, is to not split issues before a technical 
>> resolution is determined.  If we split things to early then you have two 
>> unresolved issues and risk arriving at divergent solutions to the same 
>> issue, expressed in different texts.  We don't want that to happen.  So 
>> I'm thinking that any splits (subtasks) should occur post-resolution.
> That makes a lot of sense, should be a standing rule for the resolution
> work flow.

I'm not sure if it has to be standing rule, but a rule like this seems
to be reasonable.

It may further be reasonable if we have a rule that tasks are only 
cloned (or sub tasks are only added) if the TC agrees to resolve a task 
in a particular deliverable (specification or errata). This avoids that 
we get tasks that never get resolved, because the TC never decides to 
include its resolution into an errata. It further helps to identify 
exactly that set of tasks that shall be included into a particular 

I haven't tried it, but I assume that JIRA allows to search on open and 
on closed tasks. If so, we can for instance get all candidates for an 
ODF 1.0 Errata 2 by searching for tasks whose "Affected version/s" field 
includes "ODF 1.0", and whose "Fix Version/s" field does not include 
"ODF 1.0", "ODF 1.0 (2nd edition)" or "ODF 1.0 Errata 01". We can then 
clone those tasks where we agree to include them into Errata 02, and 
have these as open tasks we can work with.

Best regards


> Best regards,
> Peter
>>> RE: [office] office-comment -> JIRA migration
>>> Concerning subtasks and issue workflow, I was able to learn some things
>>> about workflow and the benign way sub-tasks and parent tasks move 
>> through
>>> stages independently and their connection is preserved.  I did this on 
>> the
>>> OIC TC JIRA, and my summary is at
>>> <http://lists.oasis-open.org/archives/oic/200905/msg00025.html>.
>>> I'm not sure if all members of the ODF TC can browse the OIC TC JIRA, 
>> but
>>> those of us who are on that TC can do so.
>>> I am more comfortable adding comments to issues that go with the public
>>> comments I am investigating.  It is not quite so visible as making new
>>> issues or sub-tasks of issues, although commenting seems to generate as 
>> much
>>> JIRA activity reporting to the ODF TC List as anything else.
>>>  - Dennis 
>>> -----Original Message-----
>>> From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
>>> http://lists.oasis-open.org/archives/office/200905/msg00035.html
>>> Sent: Thursday, May 07, 2009 11:15
>>> To: Michael.Brauer@Sun.COM; dennis.hamilton@acm.org
>>> Cc: office@lists.oasis-open.org
>>> Subject: RE: [office] office-comment -> JIRA migration
>>> Michael, I am considering just making comments, rather than get behind 
>> in
>>> providing the actions on public comments that I have raised my hand for. 
>>> [ ... ]
>>> With regard to subtasks, those are valuable when an item applies to more
>>> than one ODF TC product.  It lets them be resolved individually.  If 
>> there
>>> is a single item that involves, say, change to the ODF 1.2 draft and 
>> also a
>>> potential erratum for a previous version, we shouldn't close the item 
>> until
>>> both have occured.  This seems like it makes management difficult and 
>> the
>>> solution is to split the tasks one way or another.  I don't know what
>>> happens when an umbrella task is resolved or closed when its subtasks 
>> are
>>> not.  I will see if I can find that out on the unused OIC JIRA where I 
>> might
>>> have more privileges.
>>>  - Dennis
>>> [ ... ]
>>> ---------------------------------------------------------------------
>>> 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 
>> ---------------------------------------------------------------------
>> 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]