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] JIRA changes

Patrick Durusau <patrick@durusau.net> wrote on 12/17/2010 03:30:40 PM:

> On Fri, 2010-12-17 at 12:56 -0500, robert_weir@us.ibm.com wrote:
> > I've made two changes to our JIRA project:
> > 
> > 1) Added a component called "change tracking".  It may be worth while 
> > assign this component to any relevant ODF-Next issues.
> > 
> Sorry, I don't understand the semantics of this component. What would it
> add to the management of ODF-Next issues?

This was a request from the new Advanced Document Collaboration SC.  This 
will make it easier for them to find existing issues related to change 
tracking as well as to associate any new related issues that may be 
entered by them.

Components generally describe the "feature" of ODF reported in the issue, 
such as text, charts, encryption. etc.  "Change tracking" was not 
previously broken out as its own component in JIRA.  Now it is.

> > 2) I've added a new release called "ODF 1.2 CD 07".  Although we have 
> > plans to approve an additional CSD, this component can be used as the 
> > for" releases for any 15-day public review comments that a member 
> > is a "must fix" item.
> I agree some mechanism is needed. But, we need a mechanism with a common
> semantic. Such as allowing any comment, TC member or otherwise, to be
> "fix for," but the TC fixes "must fix," etc. 
> The TC can make all issues "must fix" but I would really like to avoid
> the resolved, no, not resolved, etc. We need a little more process and
> people reviewing when drafts are posted. 

If you find an issue in the CSD 06, write it up in JIRA.  "Find version" 
is obviously CSD 06.  But what do you put for "Fix version"?  In some 
cases the issue author might recommend ODF-Next, which means they are 
recommending the issue be deferred.  In other cases they might think the 
issue is critical and must be fixed, in which case they would pick CSD 07. 
 We should probably also put something intermediate to indicate that the 
issue is important, but not substantive (meaning, does not involve 
conformance) in which case it could be assigned to ODF 1.2 Errata 01.

Let's see how many comments we receive in the next few weeks.  I'm a firm 
believer that with 2000 comments no process is going to work well, but 
with 5 comments almost any process will work.



> Hope you are at the start of a great weekend.
> Patrick
> > 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 

> > 

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