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

"Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 05/05/2009 
11:41:00 PM:

> 2. Wow, so we are up to 1500 this way.  For something pretty amusing, go 
> the end of the No Component list (it is the 8th page of all of them) and
> notice a sorting aberration in JIRA.  OFFICE-2 comes after OFFICE-1499.
> Heh.  Hmm, when I resort by the key that doesn't happen.  Not sure it is 
> or JIRA's default view.  Will keep watching.

We have far fewer than that.  For example there are around 300 that are 
just me responded to comments on the list.  Once we eliminate those, and 
other comments on commnets, as well as the defects that were already 
addressed in the ODF 1.0 public review, the ISO/IEC 26300 review and the 
ODF 1.0 Errata 01 comments, I think we'll be down to 500 or so.

> 3. I see that I can make sub-tasks of issues I didn't originate (such as
> OFFICE-1497) and I can comment, but I can't do anything about Components 
> Effected Versions.  I think a sub-task will let me though.  So I have 
put my
> recommendation at
> <http://lists.oasis-open.org/archives/office/200904/msg00084.html> into 
> sub-task.  But I will do it on Alex Brown's OFFICE-1493 and then see if 
> can close OFFICE-1497.  This is not necessarily the best way to handle 
> but it seems to be the only way those other than the officers can 
> additional information on these.

Ughhh,  Probably best to just add the info as a comment for now, or ask 
Michael or I to change components, etc.  You can set components and 
versions when you create an issue initially, right?  But creating subtasks 
just to change the component, and then deleting the patent tasks sounds 
like trouble, especially when we use subtasks for a legitimate purpose. 
For example, when you delete the parent, what happens to the children?

Or, if you want to be Maestro di Commenti, we could vote to approve you as 
such and then maybe Mary would give you the fuller edit rights.

> 4. In retrospect, it looks like I should have made 3 subtasks, one each 
> ODF 1.0, ODF 1.1, and 1.2, so they could be closed separately.  Bummer.
> (What I ended up with instead is OFFICE-1501.)
> Thoughts?

I assume you are using "close" loosely.  The workflow should be:

1)"Create issue"
2)"Open issue", meaning that the TC has decided to accept the issue 
something it will address.  It would be "Close issue" if the TC decided 
not to do anything, that the comment was incorrect, invalid, superseded, 
3)"Resolve issue", meaning the TC has determined the technical resolution 
to the issue
4) "Apply issue resolution", meaning the Editor has updated the text of 
the standard according to the resolution.

You can assign multiple target versions for the issue when you create the 
issue.  This can be updated when the issue is opened, resolved and 
applied.  So I don't think we need to create subtasks for that, unless we 
have something complicated, like a defect that requires a different 
technical resolution in different versions of ODF. 


>  - Dennis 
> PS: On the version of the form I see, it does say "sub-task" everywhere.
> -----Original Message-----
> From: robert_weir@us.ibm.com [mailto:robert_weir@us.ibm.com] 
> http://lists.oasis-open.org/archives/office/200905/msg00011.html
> Sent: Tuesday, May 05, 2009 18:13
> To: office@lists.oasis-open.org
> Subject: RE: [office] office-comment -> JIRA migration
> http://lists.oasis-open.org/archives/office/200905/msg00010.html
> "Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 05/05/2009 
> 05:45:27 PM:
> [ ... ]
> Thanks for pointing out the reverse order thing.  That is the order they 

> show up in the mailing list archives.  But is probably more useful for 
> to enter them in chronological order, so I'll reverse them before 
> importing.
> [ ... ]
> Yes, there is an "Edit this issue" link under "Operations" on the left 
> the issue details screen.  Do you see that?  Or is it only available to 
> Chairs?  Make sure you are logged in.
> [ ... ]
> > 3. It would be good to allow sub-tasks.  I don't see a button for 
> but
> > it may be that is because I am not the reporter.  But subtasks will be
> > useful, especially for comments that have multiple parts and/or apply
> > differently to different versions of specifications.
> > 
> They call it a "subtask".  I can see an action for that, directly above 
> "Edit this issue".
> [ ... ]
> ---------------------------------------------------------------------
> 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 

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