From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VmPlM-0004QX-Qd for qemu-devel@nongnu.org; Fri, 29 Nov 2013 10:13:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VmPlG-0004jk-Qu for qemu-devel@nongnu.org; Fri, 29 Nov 2013 10:13:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:19273) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VmPlG-0004iz-D6 for qemu-devel@nongnu.org; Fri, 29 Nov 2013 10:13:42 -0500 Message-ID: <1385738015.23450.32.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Fri, 29 Nov 2013 16:13:35 +0100 Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] seabios release planning List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: seabios Cc: qemu-devel Hi, qemu 1.7 is almost out of the door. I want update seabios early in the 1.8 devel cycle. Time to do resume the release planning since we've scratched the idea to do a last-minute bios update for 1.7. I'd like to see a seabios release from the master branch in december. Ideally we'll put a prerelease into qemu before the final release so we get some testing. We could either explicitly tag a release candidate or just grab a snapshot for that. Commit pending patches, enter seabios freeze, prepare seabios update for qemu can be done next week I think. Then have 2-3 weeks freeze period, tag final release before xmas. In case something doesn't go as planned early january. Pending patches: * my ahci and pci patches sent this week. * anything else? How we wanna call the baby? 1.7.4? 1.8.0? cheers, Gerd