<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/02/16 17:08, Cemil Azizoglu
wrote:<br>
</div>
<blockquote
cite="mid:CAB6MOpVS9v1=10s8OzcE7xEDFu+t8EuO9BdiwFEGEXWVCdQxhA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default">Hi,</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">We talked about the release process
and how it could be improved. Here are some ideas. Please add
if you have others.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">(Jenkaas could be leveraged for some)</div>
<div class="gmail_default">
<ol>
<li>Minimizing the manual steps (like creation of the next
target branch on lp, etc) using scripts/launchpad API.<br>
</li>
<li>'make release' target that 'll check for ABI breakage,
perhaps even prepopulate the changelog with some static
info, etc.</li>
<li>Downstreams' build/sanity testing could be done as part
of MP autolanding to identify breaks.<br>
</li>
<li>Downstreams' release testing. How useful are AP tests
for U8 and Browser? General opinion is 'not very'. Should
we look into doing away with them? Or at least identify
the subset of them that is relevant to Mir, and run them
during every release as part of autolanding as a
'nonblocking' test.</li>
</ol>
</div>
<div class="gmail_default">As always I'll be creating a trello
card for this.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Thanks</div>
<div>
<div class="gmail_signature">
<div dir="ltr">Cemil Azizoglu
<div>Mir Display Server - Team Lead</div>
<div>Canonical USA</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
Essentially, we have to cater for two types of release:<br>
<br>
1. release changes from (development) trunk to a brand new series;
and,<br>
2. cherry-picking from (development) trunk to an existing series
(or, very occasionally fixing on the series directly)<br>
<br>
In theory, there should be a third one: releasing changes from
development to the current series - but our server ABI isn't
sufficiently stable to do that.<br>
</body>
</html>