<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Clément,<br>
<br>
Le 31/01/2017 à 14:53, Clément David a écrit :<br>
</div>
<blockquote
cite="mid:1485870785.2059.5.camel@scilab-enterprises.com"
type="cite"><br>
<blockquote type="cite">
<pre wrap="">Finally,
</pre>
<blockquote type="cite">
<pre wrap="">Do not hesitate to ping us if you already have some bugfix commit in review on master and want
them
to be applied on the 6.0 branch.
</pre>
</blockquote>
<pre wrap=""> Doesn't the CodeReview +1 flag just mean this? I believed it does.
</pre>
</blockquote>
<pre wrap="">
Yes it does for commit to be merged *in the master branch*.
For already pushed commits that are currently in master but expected to be part of 6.0.0, you should
ask the team or re-push on refs/for/6.0 by yourself.</pre>
</blockquote>
<br>
I think that, by default, every commiter aims to propose and
actually use in Scilab <i>as soon as possible</i> the code he/she
commits , whatever is the branch. <br>
Otherwise, he/she raises a CR-1 flag or put a WIP: in the commit
message.<br>
From here, if there are restrictions to enthusiastic commits, there
are also gatekeepers :)<br>
<br>
Regards<br>
Samuel<br>
<br>
</body>
</html>