<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1251"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Peter,</div><div><br></div><div>I wasn't been searching for gerrit (search isn't brilliant and I can't build search that will show me tickets that were under review for long time, I need to go to each ticket and check), just looked to my stared changes, issues that I had some internal relation.</div><div>Couple of examples:</div><div><br></div><div><a href="http://review.whamcloud.com/#/c/3553/">http://review.whamcloud.com/#/c/3553/</a></div><div><a href="http://whamcloud.com/#/c/3277">http://review.whamcloud.com/#/c/3277/</a></div><div><a href="http://review.whamcloud.com/#/c/5213/">http://review.whamcloud.com/#/c/5213/</a></div><div><a href="http://review.whamcloud.com/#/c/4372/">http://review.whamcloud.com/#/c/4372/</a></div><div><a href="http://review.whamcloud.com/#/c/4641/">http://review.whamcloud.com/#/c/4641/</a></div><div><a href="http://review.whamcloud.com/#/c/4664/">http://review.whamcloud.com/#/c/4664/</a></div><div><a href="http://review.whamcloud.com/#/c/3725/">http://review.whamcloud.com/#/c/3725/</a></div><div><a href="http://review.whamcloud.com/#/c/2406/">http://review.whamcloud.com/#/c/2406/</a></div><div><br></div><div>Again, I don't want to start any war or discussion about those tickets, or about some other.</div><div>I don't want to blame anyone about something. But for me obviously some problems exit.</div><div><br></div><div>Those tickets are probably all have good explanation why.</div><div>My suggestion was to build process, that will resolve such issues automatically and will provide us stat and info about Sustaining review activities.</div><div>What I don't want is to do it manually.</div><div><br></div><div>What we propose is to define all stages of Sustaining process to gather all needed info to understand where we have most problems:</div><div>* review resources</div><div>* incorrect test failures</div><div>* rebases</div><div>* code freeze</div><div>* some other…</div><div><br></div><div>Process for all, not just Xyratex, but for all reviews.</div><div><br></div><div>That will give us more visibility and possibility to improve.</div><div>We are not saint and we need to improve too. We have issues with upstream submission too and there are no fault here in this discussion.</div><div><br></div><div>Right now we know that only based on our experience in our heads, intuitively.</div><div><br></div><div>Of course we could use any suggestions. If we all think that just e-mail with list will resolve this situation - we will use that.</div><div><br></div><div>I just started this topic to share our process that could be useful, and gather other feedbacks - what could be done.</div><br><div>
<div><div>Thanks,</div><div>Denis</div></div>
</div>
<br><div><div>On 7 àâã. 2013, at 19:07, "Jones, Peter A" <<a href="mailto:peter.a.jones@intel.com">peter.a.jones@intel.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Thanks Denis I would appreciate it. I absolutely agree that this needs to<br>be an iterative process and that we need data to analyze and improve.<br><br>The last time this concern was raised (just before ISC) I did complete an<br>analysis of every single Xyratex patch submitted against master and (other<br>than a couple of feature patches that had been delayed by the 2.4 feature<br>freeze) the longest wait that I saw at that time was only a few weeks.<br><br>Xyratex committed at that time to provide a consolidated list of issues<br>that are a concern. I suggest that we focus on that as a first step before<br>getting into possible process changes so that we can be sure that our<br>process reflects the actual situation.<br><br><br>On 8/7/13 8:11 AM, "Denis Kondratenko" <<a href="mailto:denis_kondratenko@xyratex.com">denis_kondratenko@xyratex.com</a>><br>wrote:<br><br><blockquote type="cite">OK, I will go and try to search.<br><br>Maybe I have overestimated that, my apologize for that - will provide you<br>numbers and examples.<br>Point wasn't in that.<br><br>Point was - we have no numbers - so nothing to analyze and improve.<br><br>Thanks,<br>Denis<br><br>On 7 àâã. 2013, at 18:03, "Jones, Peter A" <<a href="mailto:peter.a.jones@intel.com">peter.a.jones@intel.com</a>><br>wrote:<br><br><blockquote type="cite"><snip><br><br><blockquote type="cite"><br>It is not a rare occurrence - patches that were submitted 6-12 months<br>after it was first pushed for review.<br></blockquote><br>Denis, please give me three examples where patches pushed to master have<br>waited 6-12 months after being pushed for review?<br><br>I take this very seriously.<br><br>There are certainly busy times when lower priority patches might need to<br>wait but I have not seen anything that long.<br><br>Feature patches submitted during the feature freeze, but that is usually<br>more like 3-4 months in the worst case scenario.<br><br>Sometimes people push patches against maintenance branches, which can be<br>useful for the community but if these land it will only be at the time<br>we<br>create a maintenance release against that branch.<br><br><br></blockquote><br><br>-- <br><br><br>------------------------------<br>For additional information including the registered office and the<br>treatment of Xyratex confidential information please visit <a href="http://www.xyratex.com">www.xyratex.com</a><br><br>------------------------------<br>_______________________________________________<br>cdwg mailing list<br><a href="mailto:cdwg@lists.opensfs.org">cdwg@lists.opensfs.org</a><br>http://lists.opensfs.org/listinfo.cgi/cdwg-opensfs.org<br></blockquote><br></blockquote></div><br></body></html>
<br>
<pre style="white-space:pre-wrap;color:rgb(34,34,34);background-color:rgb(255,255,255)"><hr>For additional information including the registered office and the treatment of Xyratex confidential information please visit <font color="#1155cc"><a href="http://www.xyratex.com/" target="_blank">www.xyratex.com</a></font>
</pre><div><hr></div>