RE: [office-formula] Handling of JIRA issues

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

I think the problem is that the person who notices the issues might not know
what the repair is.  It could be a serious defect, but available information
in the specification is not enough to know what is intended or needed.

So we can be in a position where there is a known defect, it is clearly a
defect, but no one steps forward to resolve it, or feels able to.  What
then?

I suppose one resolution would be to remove whatever feature has the
unresolved defect, but that might not always be a very welcome solution.  I
guess we need to see what actually comes up before we decide to tie our
hands in advance.

 - Dennis

-----Original Message-----
From: Eike Rathke [mailto:erack@sun.com] 
Sent: Monday, April 19, 2010 08:16
To: OASIS ODFF SC
Subject: [office-formula] Handling of JIRA issues

Hi,

Since we're nearing CD3 and following that the hot phase of a public
review, I'd like to propose a handling of JIRA issues until CD3 and
review:

New and unassigned issues may not have a ODF 1.2 (CD3 or final) target
set unless

a) Someone commits himself to resolve the issue for a specific target.

b) The TC/SC agrees on a target for the issue AND finds someone for a).

Following that, of course it is valid to submit an issue, regard it
important enough for CD3, resolve it and target it to CD3.

However, it is invalid to submit new issues and target them to CD3 if no
one committed on resolving the issue.

Otherwise having the target doesn't make sense.
Opinions?

  Eike

-- 
Automatic string conversions considered dangerous. They are the GOTO
statements
of spreadsheets.  --Robert Weir on the OpenDocument formula subcommittee's
list.