OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

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


Subject: Re: [dita] Methods to track issues and bugs


For DocBook, we set up a project at Sourceforge and the TC uses the
bug-tracking interface for that project to track requests for
enhancements to the DocBook DTD/schema and also for bug reports and
feature requests related to the toolkit (stylesheets).

  DocBook RFE tracker
  http://sourceforge.net/tracker/?atid=384107&group_id=21935&func=browse

  other trackers
  http://sourceforge.net/tracker/?group_id=21935

We've found that to work pretty well.

As far as using the OASIS website document-management mechanism (Kavi),
I think you might want to avoid relying on it much. There are some
serious limitations and problems related to it -

  http://lists.oasis-open.org/archives/docbook-tc/200402/msg00013.html

Don Day <dond@us.ibm.com> writes:

> Real Soon Now we will need to set up standard methods to log incoming
> issues and bugs and to manage their disposition in the TC or the external
> toolkit as appropriate.  Because we are starting off with a submission that
> is already in use, we'll need to get something in place rather quickly.
> I'd appreciate insight into how to do this with OASIS mechanisms if
> possible.
> 
> This will be another item on tomorrow's agenda.
> 
> Regards,


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