Closed tomschr closed 9 years ago
We've decided to use number 1 with the following structure/tags:
<dm:bugtracker>
<url><!-- Tracker URL --></url>
<component><!-- Bugzilla component --></component>
<product><!-- Bugzilla tracker product --></product>
<assignee><!-- Name of assignee --></assignee>
<version><!-- version --></version>
</dm:bugtracker>
bugtracker
: common parent element for all bug tracker related issuesurl
: tracker URL
component
: Bugzilla component, usually Documentation
by default; not used for GitHubproduct
: Bugzilla product, for example SUSE Cloud 4
; not used for GitHubassignee
: Account name, login, or otherwise of the assigneeversion
: version of the product or releaseWe also have to update the man page.
man page has been updated: https://github.com/openSUSE/docmanager/commit/ae221a69d40fc6e34518cc71f9a340ca0372df74
Current Situation
Our related sister project openSUSE/suse-xsl needs to extend the JavaScript code (see related issue openSUSE/suse-xsl#36). At the moment, there is hard-coded information about the Bugzilla product. This is unfortunate as products will very likely change in the future.
The better solution is to move this information (and other tracker information) into the XML sources. To handle such tracker information more easily, DocManager should support that.
Suggested Solutions
DocManager should be able to store tracker information for Bugzilla & GitHub in the
<dm:docmanager>
element. Three approaches should be considered:Nested structure DM should use
<trackerinfo>
and use child elements to store its information. Pros:Cons
Flat structure Every information should map to an element name with a prefix
tracker-
. Pros:Cons
releaseinfo
to store at least some information. However, it is not really a good option as the semantics are not very appropriate.