<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">hello, team,
<div><br>
</div>
<div>Trio2o git repository is ready now: <span style="font-size: 13.3333px;">https://github.com/openstack/trio2o</span></div>
<div><br>
</div>
<div>The repository inherited all files and commit messages from Tricircle.</div>
<div><br>
</div>
<div>It's now the time start to do the tricircle splitting: a blue print is registere for <span style="font-size: 13.3333px;">Tricircle</span><span style="font-size: 13.3333px;"> </span><span style="font-size: 10pt;">cleaning: </span>https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron.<span style="font-size: 10pt;">There
are lots of documentation work to do. Please review these doc in the BP, thanks.</span></div>
<div><br>
</div>
<div>There are some proposal for patches during the splitting:</div>
<div><br>
</div>
<div>1. For patch which is already in review status, let's review it in Tricircle (no matter it's for Trio2o or Tricircle), after it's get merged, then port it to Trio2o. After all patches get merged, let's have a last tag for Tricircle to cover both gateway
and networking automation function. Then the cleaning will be done in Tricircle to make Tricircle as a project for networking automation only </div>
<div>2. For new patch which is only applicable to Trio2o, I propose that we submit such patches in Trio2o only, no need to submit in Tricircle.</div>
<div><br>
</div>
<div>Would like to know your thoughts on the splitting.</div>
<div><br>
</div>
<div>Best Regards</div>
<div>Chaoyi Huang(joehuang)</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
</div>
</body>
</html>