This is a personal view on how doxygen bugs in the debian BTS should be prioritized by the debian package maintainer. Of course this is not meant as a policy nor should it be binding on people using the BTS to report bugs.
This is a personal view on how doxygen should be maintained within debian. Of course this is not meant as a policy nor should it be binding on people using the BTS to report bugs.
## 0. Stability
...
...
@@ -6,11 +6,11 @@ Doxygen is a mature product.
It is used by many people for different purposes, and stability is more important than updating after each minor patch release (in the sense of major.minor.patch).
It is acceptable to skip patch releases if the changelog does not highlight major features, it does not close bugs we forwarded and that release is not explicitly requested by users.
It is acceptable to skip patch releases if the changelog does not contain major features, it does not close bugs we forwarded and that release is not explicitly requested by users.
## 1. Architectures
Upstream provides binaries for Linux x86-64 (“Compiled using Ubuntu 14.04 with kernel 3.13.0 and gcc 4.8.2”), Windows (32-bit and 64-bit) and Mac OS X 10.5+.
Upstream provides binaries for Linux x86-64 (“_Compiled using Ubuntu 14.04 with kernel 3.13.0 and gcc 4.8.2_”), Windows (32-bit and 64-bit) and Mac OS X 10.5+.
Debian provides it on many more architectures besides amd64, but doxygen works there only by pure luck, since upstream is not building for them nor testing it there.
...
...
@@ -25,15 +25,13 @@ According to popcon data, ATM there are at least 8381 debian users (in reality w
Among those users there are the internal users i.e. dds, dms, and anybody who needs it to build the 443 packages that build-depend on doxygen. The external users are the complement.
Based on those numbers probably the external users are one or two orders of magnitude more that the internal users.
User input is also more precious because end users do not always file a bug when their encounter an issue.
User input is also more precious because end users do not always file a bug when they encounter an issue.
Consequently the maintainer should give precedence to bugs filed by people who use doxygen directly for the purpose of generating documentation, rather than indirectly for packaging.
## 3. What is top-priority
Top-priority in this context is what affects a user's main purpose.
As a human, top-priority is remaining alive. As a singer, top-priority is avoid loosing the voice.
Top-priority in this context is what affects a user's main purpose. As a human, top-priority is remaining alive. As a singer, top-priority is avoid loosing the voice.
Out of the metaphor, for external users who use doxygen to create documentation, top-priority is an issue such as a crash that prevents them from generating the documentation.