From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8189 invoked by alias); 23 Sep 2004 12:16:15 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 8002 invoked from network); 23 Sep 2004 12:16:02 -0000 Message-ID: <4152BE80.1040201@ecoscentric.com> Date: Thu, 23 Sep 2004 12:16:00 -0000 From: Alex Schuilenburg Organization: eCosCentric Limited User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en, en-gb MIME-Version: 1.0 To: testfarm@ecoscentric.com, ecos-maintainers@ecos.sourceware.org Subject: Test Farm: MySQL upgrade X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00021.txt.bz2 All [excuse the x-post but I need to get everyone, including those external maintainers that occassionaly use the farm] We need to upgrade the MySQL database to version 4 from v3.23 for various reasons in the test farm, the largest of which is house-keeping: There are several housekeeping functions that cannot be done automatically in MySQL3.23 without writing reams of perl scripts to do this automatically. Since I am not of the disposition of writing scripts unnecessarily, I would like to upgrade. After doing various research, we should be able to move seamlessly in the farm. Bugzilla works, so the farm should too. The upgrade could take anywhere as short as an hour to as long as a couple of days if I hit problems. Needless to say, this will require syncing with releases and whatever else people are currently monitoring in the farm. I propose starting on the weekend 2nd Oct to minimise effects. This will mean shutting down the farm for that period. Please let me know if this is a problem and your preferred dates if so. Thanks -- Alex