Marco,
H. If that is the current rate of change, it may be we should delay
instituting this process a few days or a week longer.
For the moment, then, I'll urge everyone to start being more careful
about testing packages before submitting them, and to be careful about
choosing which bugs are best to work on.
- Jim
On Sun, 2007-07-15 at 02:06 +0200, Marco Pesenti Gritti wrote:
On 7/14/07, Jim Gettys [EMAIL PROTECTED] wrote:
2) if you have a package/bundle that should go in the build,
please
include a change log with references to each bug you are
fixing.
Include it directly in trac; having to excavate your change
log out of a
rpm or bundle is a bit too painful.
2) please do not assign bugs to J5 yourself; he's on vacation,
and we'll
approve all changes to the build from here on out. Right now,
we'll
(Dan Williams I'm also happy to have make these judgements)
likely be
lenient, if your judgment seems sensible. Approval is made
when Dan or I
assign the trac item to Dan Winship (who is our new build
tzar), to
include. The bar will be lifted higher as the days go by.
Jim,
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?
Marco
--
Jim Gettys
One Laptop Per Child
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
