From owner-freebsd-ports@FreeBSD.ORG Tue Jun 3 15:48:21 2014 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 458698C5 for ; Tue, 3 Jun 2014 15:48:21 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05AE12957 for ; Tue, 3 Jun 2014 15:48:21 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1Wrqwm-000Ckw-6p; Tue, 03 Jun 2014 17:48:20 +0200 Date: Tue, 3 Jun 2014 17:48:20 +0200 From: Kurt Jaeger To: Fbsd8 Subject: Re: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla Message-ID: <20140603154820.GI2341@home.opsec.eu> References: <92E4FB10-DDC8-4B3E-9242-4E8494491630@FreeBSD.org> <538DBAEC.5060905@gmail.com> <538DE738.1000401@a1poweruser.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <538DE738.1000401@a1poweruser.com> Cc: ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 15:48:21 -0000 Hi! > This is the first I have seen this GNATS to Bugzilla subject discussed. It was discussed on https://wiki.freebsd.org/Bugtracking since approx. 2004. > GNATS has been working just fine for many years, why the change to Bugzilla? See the wiki page for the details. > Who makes this kind of change in a vacuum? It was discussed on the committers list, and some people worked for a long time. > WHO AUTHORIZED THIS???? The first mention to replace gnats with bugzilla apparently was around 2001 (yes, that long ago!) > Why was the ports mailing list not included in this before now? It was mentioned on the ports@ list in the past, but there was no real 'driver' mentioned, but now it happened. The BSDCan 2014 meeting was the final trigger to switch over. So, it took a looooong time and now it happened. It will take a bit to get all the kinks out, but it looks like progress 8-) -- pi@opsec.eu +49 171 3101372 6 years to go !