<br><br><div><span class="gmail_quote">On 7/14/07, <b class="gmail_sendername">Jim Gettys</b> <<a href="mailto:jg@laptop.org">jg@laptop.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>2) if you have a package/bundle that should go in the build, please<br>include a change log with references to each bug you are fixing.<br>Include it directly in trac; having to excavate your change log out of a<br>rpm or bundle is a bit too painful.
<br>2) please do not assign bugs to J5 yourself; he's on vacation, and we'll<br>approve all changes to the build from here on out. Right now, we'll<br>(Dan Williams I'm also happy to have make these judgements) likely be
<br>lenient, if your judgment seems sensible. Approval is made when Dan or I<br>assign the trac item to Dan Winship (who is our new build tzar), to<br>include. The bar will be lifted higher as the days go by.</blockquote>
<div><br><br>Jim,<br>
<br>
I'm building several packages every day which goes to the OLPC-2 branch
and hence are included in the builds. How do you want to deal with the
approval process for these? Should I post a ticket and get approval for
them before doing the build?<br>
<br>
Marco<br><br>
</div></div>