On Thu, Dec 11, 2008 at 04:24:32PM -0500, Eben Eliason wrote: > 1) Joyide is the development build stream. It doesn't by any means > promise stability, in general. > 2) It's early in the release cycle, so things are even more likely to > break in fairly big ways.
It is as if joyride is being used as part of developers' edit, compile and test sequence. Wouldn't it be more appropriate to do this sequence privately before a developer releases their changes to the public? Here's how it would happen ... the developer would build a new RPM, install it on a test unit, test that it works, *before* publishing the RPM for the joyride to pick up. If any failures occur due to integration against other developer changes, then stronger dependencies should be added. I'm also waiting for the joyride builds to be usable before I consume download data resources on them. -- James Cameron mailto:qu...@us.netrek.org http://quozl.netrek.org/ _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
