Hi,
On Wed, Jan 28, 2015 at 09:34:28PM +0100, Lionel Elie Mamane wrote:
1) There doesn't seem to be a project/component on Bugzilla for
problems with the bugzilla installation.
2) Component ci-integration should maybe migrate off "LibreOffice"
into its own, or together with the above or into an "infra" project
or something like that? I admit that this is debatable.
Both are valid points. However, TDF infrastructure has:
https://redmine.documentfoundation.org/projects/infrastructure
IMHO these are the options:
1/ Infra tracking issues on both Bugzilla and on Redmine.
There is no way in which this can be a desireable scenario.
2/ Infra tracking issues only on Bugzilla. For someone working in dev or QA
certainly desirable as we use Bugzilla. However, the infra team seems to
prefer Redmine over Bugzilla and we wouldnt close Redmine as a lot more
subprojects are using it.
3/ Infra tracking issues only on Redmine. Certainly not ideal, but IMHO the
best and most realistic option given how this grew historically.
To make 3/ more bearable, we should likely close and move all infra and
ci-integration issues to Redmine. It might also possibly be helpful to have a
bot that:
a/ Scans for new ci-integration and infra bugs
b/ Creates Redmine tickets from them (e.g. via the email interface of Redmine)
c/ links to the Redmine ticket on Bugzilla and closes the bug on Bugzilla as
"RESOLVED/MOVED".
Anyone writing such scripting is welcome, I guess.
See also:
https://redmine.documentfoundation.org/issues/209
https://redmine.documentfoundation.org/issues/1055
Best,
Bjoern
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.