<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>Why couldn't Bob harvest changes from Mantis so they can be reviewed and<br>posted to trunk?<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><div><br></div>1) Because trunk is a moving target. The principle is that mantis needs to manage fixes relative to an actual release. So that you can take a production image and fix bits you need to to keep current. If you are harvesting fixes from mantis into trunk then you will be adjusting the fixes to be appropriate to "trunk" (a moving target). </div><div><br></div><div><div>Bob isnt only about harvesting fixes.</div><div><br></div></div><div>2) If you are the developer of a package that loads in all forks, you are supported by the ability to load fixes into the other forks you support. The trunk process doesn't care about supporting you to keep your package working.</div><div><br></div><div>Every change made to trunk is made to trunk only, the implications on that change to the packages that you may wish to load is not tested. That is what bob was designed to do, to test the whole, and to test all derived images.</div><div><br></div><div>2) The bob process is intended to be used in regular cycles, to generate multiple artifacts, that may then be integrated. Trunk messes this up by prolonging the release cycle to years to produce one artifact.<br><br></div>Keith</body></html>