linux-kernel - Re: linux-next: taking a break

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOesGMjO0JQ8Whm_MEXrOnFFPAG8MXBiQpddV6e8jRR6rcCkTQ@mail.gmail.com>
Date:	Thu, 19 Sep 2013 21:56:55 -0700
From:	Olof Johansson <olof@...om.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	Linus <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"ksummit-2013-discuss@...ts.linuxfoundation.org" 
	<ksummit-2013-discuss@...ts.linuxfoundation.org>
Subject: Re: linux-next: taking a break

On Thu, Sep 19, 2013 at 9:46 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> I will be having a 3 week break leading up to the kernel
> summit.  This means that next-20130927 (next Friday) will be the last
> linux-next release until next-20131028 (or maybe 29 depending on
> jetlag).  I presume that Linus will be up to v3.12-rc7 by then and -rc7
> is often the last before a release ... Please plan accordingly.

This brings up a subject that could be good to discuss at KS: Do you
want a backup to share your workload and for hand-off at times like
this?

You've been carrying the load of linux-next alone for years now, and
having someone that can take over every now and then seems like a good
idea. You've been doing an outstanding job but everybody need downtime
sometimes.

Linux-next is incredibly valuable for _so_ many of us, and a big part
of the value is in the continuous frequent releases that allows us to
catch issues quickly when they are staged, and keep bisectability as
high as possible. It also helps us discover early on when someone is
merging code through a maintainer they shouldn't (due to conflicts).
It will be very much missed during your well-deserved vacation.

-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/