2010/8/18 Cliff Brake <[email protected]>: > On Wed, Aug 18, 2010 at 4:30 AM, Martyn Welch <[email protected]> wrote: >> On 17/08/10 16:02, Cliff Brake wrote: >>> >>> I think it would be very useful to have a "stable" branch that is only >>> synchronised with dev when X number of targets build from a clean >>> build. It seems like this would be high value, with little effort. >>> Of course there will be corner things that break, but at least a new >>> beagleboard user can check out something and have reasonable >>> confidence that it will build images. >>> >>> Does anyone have suggestions for the branch name and a reasonable >>> subset of machines and build targets? Perhaps someone is already >>> running these clean builds? At one point we had a machine at OSUOSL >>> dedicated to this purpose, but no one ever set it up. >>> >> >> So something like Debian's stable, testing and unstable[1]? > > That sounds good to me -- so how about org.openembedded.dev and > org.openembedded.testing branches?
Good plan! > > I'll plan to start doing a clean build of dev every Monday for the > Beagleboard, and then merge to testing once it builds. Initial > targets: Cool! > > Angstrom Distro > beagleboard/beagleboard-linuxtag2010-demo-image > x86/minimal-image It would be nice to have some additional distro's (e.g. minimal, shr) and machines (what would be a good coverage here) tested before it is pushed > > My workstation runs a 64-bit OS, so that is probably worst case > (compared to i686). > What OS? If you want to make things really nasty go to RHEL4 (but I think most people would be fine with e.g. ubuntu 10.04) Ideally you'd do this in a clean vm to make sure that there is no dependency on whatever happens to be installed on your workstation for other purposes. Frans _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
