From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 12 Sep 2016 19:14:50 +0200 From: Greg KH To: Mark Brown Message-ID: <20160912171450.GB27349@kroah.com> References: <57C78BE9.30009@linaro.org> <20160902134711.movdpffcdcsx6kzv@thunk.org> <20160910120055.gr2cvad7efwci4f2@thunk.org> <20160912162714.GC27946@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160912162714.GC27946@sirena.org.uk> Cc: Tsugikazu Shibata , "ltsi-dev@lists.linuxfoundation.org" , "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] [LTSI-dev] [Stable kernel] feature backporting collaboration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Sep 12, 2016 at 05:27:14PM +0100, Mark Brown wrote: > > Personally I think what we've got at the minute with the > preannouncements is fairly good, though it might help if it were a bit > more explicit when announcements would be made - the change to > preannouncements at a less awkward point in the release cycle has helped > for the users I talk to but there was always a very awkward period where > people were looking for an announcement but no information to base > things on. So, where should I do this "announcement" that will be seen by everyone? And remember, we are just trying out the "preanounce" thing this time, let's see what happens, I'm not guaranteeing I will keep doing it... thanks, greg k-h