<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hej,<br>
<br>
I saw that as well and I'm in general fine with it, as I anyhow
flag my changes as WIP if I have them in draft stage. I have to
read up on it a bit more but I think changes should be moved to
WIP status by default, and if individual devs want to move them to
private later that should work.<br>
<br>
Cheers<br>
<br>
Paul<br>
</p>
<br>
<div class="moz-cite-prefix">On 2018-08-27 10:25, Mark Abraham
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMNuMASU6ozrtcvgsmBxzw5=Y_z46g=79qO13VunwrWStAbjyA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">Hi,
<div><br>
</div>
<div>We'll probably upgrade gerrit to 2.15 shortly, and Stefan
noted that it will change the way drafts are organized.
Instead of an individual patch set being a draft, the whole
change is flagged work in progress within the Gerrit metadata.
I think that, and the automated change of stuff on upgrades
will be fine for us, but I thought I would flag that for those
of you who use drafts. In principle, code could change its
visibility through the migration process. I can't see all of
the drafts, so I don't know who you all are ;-)</div>
<div><br>
</div>
<div>Info: <a
href="https://www.gerritcodereview.com/2.15.html#support-for-draft-changes-removed"
moz-do-not-send="true">https://www.gerritcodereview.com/2.15.html#support-for-draft-changes-removed</a></div>
<div><br>
</div>
<div>Mark</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>