Rob,
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.
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:]
>> http://lists.oasis-open.org/archives/office/200905/msg00035.html
>> Sent: Thursday, May 07, 2009 11:15
>> To: ;
>> Cc:
>> 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
>
>
--
Peter Junge
Open Source Strategy Director
Beijing Redflag Chinese 2000 Software Co., Ltd.
Building No.2, Block A, Huilongsen, 18 Xihuan Nanlu
Beijing Economic-Technological Development Area
100176 Beijing - P.R.China
北京红旗中文贰仟软件技术有限公司
地址：北京经济技术开发区（亦庄）西环南路18号汇龙森A座二层
邮编：100176
电话/Tel: +86-10-51570010 ext.6183
邮箱/e-mail：
http://www.RedOffice.com
