From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Haigh Subject: Re: RFC: change to 6 months release cycle Date: Mon, 5 Oct 2015 22:44:30 +1100 Message-ID: <5612629E.8020003@crc.id.au> References: <20151002174356.GA3577@zion.uk.xensource.com> <5612755302000078000A8114@prv-mh.provo.novell.com> <20151005112357.GC29124@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4490759215458201013==" Return-path: In-Reply-To: <20151005112357.GC29124@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============4490759215458201013== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4prfq5089LQuUkRA1Q21M83OMlKlqm1n5" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4prfq5089LQuUkRA1Q21M83OMlKlqm1n5 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 5/10/2015 10:23 PM, Wei Liu wrote: > On Mon, Oct 05, 2015 at 05:04:19AM -0600, Jan Beulich wrote: >>>>> On 02.10.15 at 19:43, wrote: >>> The main objection from previous discussion seems to be that "shorter= >>> release cycle creates burdens for downstream projects". I couldn't >>> quite get the idea, but I think we can figure out a way to sort that >>> out once we know what exactly the burdens are. >> >> I don't recall it that way. My main objection remains the resulting >> higher burden of maintaining stable trees. Right now, most of the >> time we have two trees to maintain. A 6-month release cycle means >> three of them (shortening the time we maintain those trees doesn't >> seem a viable option to me). >> >> Similar considerations apply to security maintenance of older trees. > Just to throw around some ideas: we can have more stable tree > maintainers, we can pick a stable tree every X releases etc etc. So everyone else in the industry is increasing their support periods for stable things, and we're wanting to go the opposite way? Sorry - but this is nuts. Have a stable branch that is actually supported properly with backports of security fixes etc - then have a 'bleeding edge' branch that rolls with the punches. Remember that folks are still running Xen 3.4 on EL5 - and will be at least until 2017. I still run the occasional patch for 4.2, and most people are on either 4.4 or testing with 4.5 when running with EL6. EL6 is supported until November 30, 2020. EL7 until 2024. People are not exactly thrilled with EL7 in the virt area - but will eventually move to it (or directly to EL8 or EL9). The 6 month release cycle is exactly why people don't run Fedora on their production environments. Why are we suddenly wanting the same release schedule for Xen? Sorry - but I'm VERY much against this proposal. Focus on stable and complete, not Ooohhhh Shiny! --=20 Steven Haigh Email: netwiz@crc.id.au Web: http://www.crc.id.au Phone: (03) 9001 6090 - 0412 935 897 --4prfq5089LQuUkRA1Q21M83OMlKlqm1n5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWEmKoAAoJEEGvNdV6fTHcQrwP/0/Wc4O/2vFDVEmkaNAhxfZ2 6w/MsLMLnFRwWv2A3u6ytNZwGX07vJkZ901FK7GiXf+QLuLPXMXdlRXy5HrKzmQH M9rfmbZBXXv2pW2UVEg/RZbwopd+UCHaSfMFJEtt2s2+KrzClc0WNO+7uipm2Jeu fFAPBTluXJyA1FemznVDBiUkjWdJUoy1g1TEB3z+TOLx+gOa7GHkwuAnWAVr/BpP wmzjvQ0n84/RECFsL73lyt9nK8JJYcfKHr5NqDJPzyyY21XLI1aeVjzPE6plKPfI FiAiH3M74JNwGkTXbq5teKTgliXd2n1hZXRYUgUgGGrjpPiqEB/z2FKnC9WCk5mj y7vnMwTHv/3o6DhsnvjMTTKYDx9ZfQWnSw5jc/3DL+WC/KkPQt5yfISYf+LhUmtg RT0qT/1ywtcY1lCvfVaE6c9YqyKqC42GpIpeATNGK4ZtYT65ViOTMFcYmh2zr5Jl LOXt9k5nN97c+OGobLUp/Vda8TehZNOTl861r24K/TycalcVcNNv50tDXSSNiMiV O5YAHI6+JVn/klVfeTgbk8xMaLq5vJa16zoN4WvnCZtgMFDhxPd46LDzBb9tXEiY 1+d7yatsad+G9JFVmkrTY6/51dzjhc0VAJVsd8bweslLIGrNsG870iWdnC1X+fwn d5D6Okkx9jzQxKyf3MeA =qH/B -----END PGP SIGNATURE----- --4prfq5089LQuUkRA1Q21M83OMlKlqm1n5-- --===============4490759215458201013== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============4490759215458201013==--