<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Sorry if touch 3<sup>rd</sup> rail.<o:p></o:p></p>
<p class="MsoNormal">But should backport bug fixes to older releases be done in distros and not upstream?<o:p></o:p></p>
<p>-----Original Message-----<br>
From: Walter A. Boring IV [mailto:walter.boring@hpe.com] <br>
Sent: Tuesday, August 09, 2016 12:34 PM<br>
To: openstack-dev@lists.openstack.org<br>
Subject: Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers<br>
<br>
On 08/08/2016 02:28 PM, Ihar Hrachyshka wrote:<br>
> Duncan Thomas wrote:<br>
><br>
>> On 8 August 2016 at 21:12, Matthew Treinish <br>
>> wrote:<br>
>> Ignoring all that, this is also contrary to how we perform testing in <br>
>> OpenStack.<br>
>> We don't turn off entire classes of testing we have so we can land <br>
>> patches, that's just a recipe for disaster.<br>
>><br>
>> But is it more of a disaster (for the consumers) than zero testing, <br>
>> zero review, scattered around the internet <br>
>> if-you're-lucky-with-a-good-wind you'll maybe get the right patch <br>
>> set? Because that's where we are right now, and vendors, distributors <br>
>> and the cinder core team are all saying it's a disaster.<br>
><br>
> If consumers rely on upstream releases, then they are expected to <br>
> migrate to newer releases after EOL, not switch to a random branch on <br>
> the internet. If they rely on some commercial product, then they <br>
> usually have an extended period of support and certification for their <br>
> drivers, so it’s not a problem for them.<br>
><br>
> Ihar<br>
This is entirely unrealistic. Force customers to upgrade. Good luck <br>
explaining to a bank that in order to get their cinder driver fix in, they have to upgrade their entire OpenStack deployment. Real world customers simply will balk at this all day long.<br>
<br>
Walt<br>
><br>
> ______________________________________________________________________<br>
> ____<br>
><br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <br>
> OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p>
</div>
</body>
</html>