<html><body>
<p><font size="2" face="sans-serif">John, </font><br>
<br>
<font size="2" face="sans-serif">Do it make sense to support storage policy work in devstack so that it can be more easily tested?</font><br>
<br>
<font size="2" face="sans-serif">-Edward Zhang</font><br>
<br>
<br>
<img width="16" height="16" src="cid:2__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt="Inactive hide details for John Dickinson ---2014-05-24 ÉÏÎç 06:27:13---John Dickinson <me@not.mn>"><font size="2" color="#424282" face="sans-serif">John Dickinson ---2014-05-24 ÉÏÎç 06:27:13---John Dickinson <me@not.mn></font><br>
<br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td style="background-image:url(cid:3__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com); background-repeat: no-repeat; " width="40%">
<ul style="padding-left: 72pt"><font size="1" face="sans-serif"><b>John Dickinson <me@not.mn></b></font><font size="1" face="sans-serif"> </font>
<p><font size="1" face="sans-serif">2014-05-24 ÉÏÎç 06:27</font>
<table border="1">
<tr valign="top"><td width="168" bgcolor="#FFFFFF"><div align="center"><font size="1" face="sans-serif">Please respond to<br>
"OpenStack Development Mailing List \(not for usage questions\)" <openstack-dev@lists.openstack.org></font></div></td></tr>
</table>
</ul>
</td><td width="60%">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img width="58" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""><br>
<div align="right"><font size="1" face="sans-serif">To</font></div></td><td width="100%"><img width="1" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""><br>
<ul style="padding-left: 7pt"><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>, openstack-operators@lists.openstack.org</font></ul>
</td></tr>
<tr valign="top"><td width="1%"><img width="58" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""><br>
<div align="right"><font size="1" face="sans-serif">cc</font></div></td><td width="100%"><img width="1" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""><br>
</td></tr>
<tr valign="top"><td width="1%"><img width="58" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""><br>
<div align="right"><font size="1" face="sans-serif">Subject</font></div></td><td width="100%"><img width="1" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""><br>
<ul style="padding-left: 7pt"><font size="1" face="sans-serif">[openstack-dev] [Swift] storage policies merge plan</font></ul>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="58"><img width="1" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""></td><td width="336"><img width="1" height="1" src="cid:4__=C7BBF676DFB865368f9e8a93df938@cn.ibm.com" border="0" alt=""></td></tr>
</table>
</td></tr>
</table>
<br>
<tt><font size="2">We've been working for a long time on the feature/ec branch in the swift repo. It's now "done" and needs to be merged into master to be generally available.<br>
<br>
Here's how the integration is going to work:<br>
<br>
1) The feature/ec branch will be refactored into a series of dependent reviewable patches<br>
2) The patch chain will be proposed to master, and master will enter a freeze until the storage policy patches land<br>
3) The first patch in the chain will be marked as -2 to "plug" the chain<br>
4) The Swift community will review and approve all patches in the chain.<br>
5) When all patches in the chain are approved, the first -2 will be removed and the whole chain will be sent to the CI system<br>
<br>
<br>
There are two things that I'll ask of you during this time. First, please commit time to reviewing the storage policy patches. Second, please do not deploy a version of Swift that is midway through the storage policy patch chain. I don't expect it to break anything, but it's a complicating factor best to be avoided.<br>
<br>
I will send out another email when the patch chain has been proposed to master and to announce the freeze.<br>
<br>
--John<br>
<br>
<br>
<br>
</font></tt><i>(See attached file: signature.asc)</i><tt><font size="2">_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
</font></tt><br>
</body></html>