Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753050Ab3HUUyF (ORCPT ); Wed, 21 Aug 2013 16:54:05 -0400 Received: from mail-vc0-f176.google.com ([209.85.220.176]:55517 "EHLO mail-vc0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752950Ab3HUUyD (ORCPT ); Wed, 21 Aug 2013 16:54:03 -0400 MIME-Version: 1.0 In-Reply-To: <20130821200034.GA10671@nazgul.tnic> References: <20130820224032.GA20491@kroah.com> <521504D7.7090204@wwwdotorg.org> <20130821200034.GA10671@nazgul.tnic> Date: Wed, 21 Aug 2013 13:54:01 -0700 Message-ID: Subject: Re: Proposed stable release changes From: Tony Luck To: Borislav Petkov Cc: Linus Torvalds , Stephen Warren , Greg KH , Andrew Morton , stable , lwn@lwn.net, Guenter Roeck , Hugh Dickins , Johannes Berg , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 974 Lines: 20 On Wed, Aug 21, 2013 at 1:00 PM, Borislav Petkov wrote: > We don't want to run daily snapshots of your tree though, right? Only > -rcs because the daily states are kinda arbitrary and they can be broken > in various ways. Or are we at a point in time where we can amend that > rule? If *nobody* runs daily snapshots - then problems just sit latent all week until the -rc is released and people start testing. Doesn't sound optimal. Running daily git snapshots can be "exciting" during the merge window. But I rarely see problems running a random build after -rc1. If you are still running that ancient 3.11-rc6 released on Sunday - then you are missing out on 28 commits worth of goodness since then :-) -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/