On Mon, Jul 19, 2010 at 9:09 AM, Keir Fraser <[email protected]> wrote: > No we have a tarball snapshot of the git repository, originally taken in > September 2008 and never updated since. The issue here is that afaik you > don't do releases out of your repository, so it's not like we could pull > your repo and check out a tagged release. I could clone your repo in our > build system, and check out a known changeset which I update across stable > releases of Xen, I suppose. The original thinking is that I want our builds > to be reasonably deterministic, and taking a snapshot tarball is easy. > > Is there any structure in your git repo in terms of stable versus > development branches? That is, are we guaranteed to get a pretty good set of > bits generated from any pull of the main branch of your public repository?
We treat master as a stable branch, and keep untested/unreviewed features in individual developers' feature branches until they've been tested/reviewed enough to be suitable to merge to stable. We're thinking about adding a development branch to speed up the development process somewhat, but whether or not that happens, gpxe.git/master will remain stable and safe to pull from. -- Josh > > Thanks, > Keir > > > _______________________________________________ > gPXE-devel mailing list > [email protected] > http://etherboot.org/mailman/listinfo/gpxe-devel > _______________________________________________ gPXE-devel mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe-devel
