[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Wed, 2013-11-27 at 17:17 +0000, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH] Update QEMU_UPSTREAM_REVISION"):
> > Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
> > ---
> > the commit sha correspond to the last tree that pass the qemu-xen push
> > gate (master).
> > 
> > Should we change this value to master once a release is done, during the
> > developpement phase?
> Perhaps we should change it to master now.  That way if further
> updates are made to the tree, and pass the push gate, they will be
> included.  Which is surely the intent ?

It looks like it was "master" until 4de97462d34f when it was updated to
"qemu-xen-4.3.0-rc1" (presumably in anticipation of branching or
releasing the rc) then it was turned into a sha at 1fee00908ae9 -- which
I think was likely to have been in error.

I agree that at least during the development phases it should be

It should probably be a tag for a release, including rcs, so that they
refer to a single consistent thing.

Given our policy of branching in the later rcs I'm not sure how we can
deal with this other than as we attempted last time by committing
something other than "master" to xen.git:Config.mk and remembering what
to do to put it back later afterwards. (or by revisiting the branching
policy, but I don't think this issue is reason enough to change).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.