<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div><br></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Christopher Yeoh <<a href="mailto:cbkyeoh@gmail.com">cbkyeoh@gmail.com</a>><br><span style="font-weight:bold">Reply-To: </span> "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><span style="font-weight:bold">Date: </span> Sunday, December 1, 2013 12:25 AM<br><span style="font-weight:bold">To: </span> "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [openstack-dev] [nova] why are we backporting low priority v3 api fixes to v2?<br></div><div><br></div><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 1, 2013 at 8:02 AM, Matt Riedemann <span dir="ltr">
<<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've seen a few bugs/reviews like this [1] lately which are essentially backporting fixes from the nova openstack v3 API to the v2 API. While this is goodness for the v2 API, I'm not sure why we're spending time on low priority bug fixes like this for the v2
API when v3 is the future. Shouldn't only high impact / high probability fixes get backported to the nova v2 API now? I think most people are still using v2 so they are probably happy to get the fixes, but it kind of seems to prolong the inevitable.<br><br>
Am I missing something?<br><br></blockquote><div><br></div><div>The V2 API is going to be with us for quite a while even if the as planned V3 API becomes official with<br>
the icehouse release. At the moment the V2 API is still even open for new features - this will probably<br>
change at the end of I-2. <br><br></div><div>I agree those bugs are quite low priority fixes and the V3 work is a lot more important, but I don't think we should blocking<br>
them yet. We should perhaps reconsider the acceptance of very low priority fixes like you reference towards or at the end of<br>
Icehouse. </div></div></div></div></div></div></span><div><br></div><div>[Gary] I agree, we should not be blocking these. I think that we should pay attention to issues that are just dealt with in V2 and make sure that those are actually addressed in V3.</div><span id="OLK_SRC_BODY_SECTION"><div><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div><br></div><div>Chris<br></div><br></div></div></div></div></div></span></body></html>