Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-20 Thread David Runge
Sorry for being late to the party. On 2017-11-14 20:30:21 (+0100), Jelle van der Waa wrote: > It seems to be time to move on, and Bugzilla is one of the more active and > maintained bugtrackers out there. Used by several big projects such as > Gnome, LLVM and Mozilla. One of the benefits of moving

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-18 Thread Jelle van der Waa
On 11/16/17 at 02:01pm, Morten Linderud wrote: > On Tue, Nov 14, 2017 at 08:30:21PM +0100, Jelle van der Waa wrote: > > [snip] > > # Products > > > > * Arch packages (core/extra or split this up) > > * Community packages (community) > > * Pacman > > * AURWeb > > * Keyring > > * Archweb (new) > > *

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-16 Thread Morten Linderud
On Tue, Nov 14, 2017 at 08:30:21PM +0100, Jelle van der Waa wrote: > [snip] > # Products > > * Arch packages (core/extra or split this up) > * Community packages (community) > * Pacman > * AURWeb > * Keyring > * Archweb (new) > * Arch VM / Docker images (new) > * Release engineering > I think co

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-15 Thread Giancarlo Razzolini
Em novembro 15, 2017 6:07 Lukas Fleischer escreveu: However, we should make sure that the old Flyspray URLs still work (and redirect to the Flyspray archive). Even though flyspray URL's are not really flyspray's and are more nginx's [0], if there is no clash with bugzilla, I don't see any reaso

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-15 Thread Florian Pritz via arch-dev-public
On 15.11.2017 09:07, Lukas Fleischer wrote: > Generally speaking, I am in favor of setting up a fresh Bugzilla > instance and not doing any sort of migration. The idea of switching to a > new bug tracker came up at least four years ago and my feeling is that > all this migration work is what was ho

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-15 Thread Jelle van der Waa
On 11/15/17 at 09:07am, Lukas Fleischer wrote: > On Tue, 14 Nov 2017 at 20:30:21, Jelle van der Waa wrote: > > It's time to switch our to something which is maintained and can be > > extended to > > our wishes. Flyspray isn't actively maintained, has had several security > > issues [1] [2]. > > [

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-15 Thread Lukas Fleischer
On Tue, 14 Nov 2017 at 20:30:21, Jelle van der Waa wrote: > It's time to switch our to something which is maintained and can be extended > to > our wishes. Flyspray isn't actively maintained, has had several security > issues [1] [2]. > [...] Great! > # Migration > > There are several options

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Giancarlo Razzolini
Em novembro 14, 2017 17:30 Jelle van der Waa escreveu: It's time to switch our to something which is maintained and can be extended to our wishes. Flyspray isn't actively maintained, has had several security issues [1] [2]. Being the person responsible for writing our flyspray ansible's role a

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Bartłomiej Piotrowski
On 2017-11-14 22:59, Allan McRae wrote: > On 15/11/17 07:34, Bartłomiej Piotrowski wrote: >>> There are several options for migrating the bug history to Bugzilla and a >>> few options are under >>> debate. (input welcome) >> As I said multiple times on IRC, I'm for starting from scratch. There >>

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Allan McRae
On 15/11/17 07:34, Bartłomiej Piotrowski wrote: >> There are several options for migrating the bug history to Bugzilla and a >> few options are under >> debate. (input welcome) > As I said multiple times on IRC, I'm for starting from scratch. There > are way too many inactive or/and incorrect bugs

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Gaetan Bisson
[2017-11-14 22:11:02 +0100] Johannes Löthberg via arch-dev-public: > My first reaction is that it'd be nice to not have a bunch of old cruft > around, For what it's worth: I completely agree. My choice would be to start over with a clean bug tracker and not migrate anything. Everyone who cares w

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Bartłomiej Piotrowski
On 2017-11-14 20:30, Jelle van der Waa wrote: > Used by several big projects such as Gnome, LLVM and Mozilla GNOME will probably end up switching to Gitlab. (Not dismissing the fact that bugzilla is rather popular choice.) > # Migration > > There are several options for migrating the bug history

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Eli Schwartz
On 11/14/2017 02:30 PM, Jelle van der Waa wrote: > There are several options for migrating the bug history to Bugzilla > and a few options are under debate. (input welcome) > > * No migration at all > * Migrate open bugs > * Migrate open bugs and auto-closing them > * Migrate all bugs > * Migrate

Re: [arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Johannes Löthberg via arch-dev-public
Quoting Jelle van der Waa (2017-11-14 20:30:21) > There are several options for migrating the bug history to Bugzilla and a few > options are under > debate. (input welcome) > > * No migration at all > * Migrate open bugs > * Migrate open bugs and auto-closing them > * Migrate all bugs > * Migrat

[arch-dev-public] Switching the bugtracker to Bugzilla

2017-11-14 Thread Jelle van der Waa
It's time to switch our to something which is maintained and can be extended to our wishes. Flyspray isn't actively maintained, has had several security issues [1] [2]. It seems to be time to move on, and Bugzilla is one of the more active and maintained bugtrackers out there. Used by several big