From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 13 Sep 2016 00:45:48 +0100 From: Mark Brown To: Greg KH Message-ID: <20160912234548.GL27946@sirena.org.uk> References: <57C78BE9.30009@linaro.org> <20160902134711.movdpffcdcsx6kzv@thunk.org> <20160910120055.gr2cvad7efwci4f2@thunk.org> <20160912162714.GC27946@sirena.org.uk> <20160912171450.GB27349@kroah.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gBMNUjqROSlRgKnE" Content-Disposition: inline In-Reply-To: <20160912171450.GB27349@kroah.com> 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: , --gBMNUjqROSlRgKnE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 12, 2016 at 07:14:50PM +0200, Greg KH wrote: > On Mon, Sep 12, 2016 at 05:27:14PM +0100, Mark Brown wrote: > > 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? I don't think it's a problem with location at the minute since you're fairly quick at posting on your G+ and blog (though I didn't spot anything on the stable list, it's possible I just can't see it due to the volume there though), that was more about the old pre v4.4 days. > 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... Sure, and I think the main thing I'm saying here is that this lack of predictability in your future plans is something the people I talk to=20 mention and may be what Shibata-san was getting at also. Part of the problem when the announcement was done after the release was that there was a lot of trying to read the runes and guess what'll happen and when going on behind the scenes, if people would like to follow the LTS but also have product deadlines they can end up walking a tightrope with their schedule and trying to predict LTS. What you did with v4.4 (announcing during the -rc cycle) addresses this, as does what you've done this year pulling that even further forwards. =20 If things don't work out with what you're doing with the preannouncement it might be good to comment on that that and say you intend to do something different next year, but hopefully everything will be fine of course. --gBMNUjqROSlRgKnE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX1z4qAAoJECTWi3JdVIfQLtUH/jWFpLGJNoqa6EtEN4149HUG U9rYF6c3c3xkpawUDDFpsBA4H8GvQPoPlLSjtXvp62nG2bi3ox0BZJeyy6CC7RzM r7WUSTZO+ZlnxpCAjuSxkxPLqCi/Zelun3WWL75dj5uiQRqH98V7nczuVmff0MIf Wy0/IHlM16khGBf4sZEBnpDKu/HSq+ANqha4R7CLCKc+o9SIhGxorWcp7JuUXdq8 2bykOk02oGJNxoTedE3tjIc/ytKYZetAklGoNyxUk647fBx2BICSLBPNLHh9IfNg Jybp9HfqiCVRXYIY9oAV0CitGyx78Bx3q2v0lXvLivKFCF0NoiOENHI0G0HXfsM= =Qbw0 -----END PGP SIGNATURE----- --gBMNUjqROSlRgKnE--