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

Re: [Xen-devel] Time for 4.2.0 rc0?

Keir Fraser writes ("Re: [Xen-devel] Time for 4.2.0 rc0?"):
> On 30/07/2012 13:37, "Ian Campbell" <Ian.Campbell@xxxxxxxxxx> wrote:
> > Not so far as I know. Ian?
> I think Ian also has a checklist of things to do before a major release.
> Might be worth running through those ahead of the first RC, too.

Looking at that:

- we aren't branching now I take it, so the entries in it relating to
   branching aren't relevant

- the following entries may be relevant:

 * consider bumping sonames of shlibs

    I think we have been trying to do this as we went along.
    Libraries which _aren't_ updated are
        libblktap.so.3.0 -> libblktap.so.3.0.0*
        libblktapctl.so.1.0 -> libblktapctl.so.1.0.0*
        libfsimage.so.1.0 -> libfsimage.so.1.0.0*
        libvhd.so.1.0 -> libvhd.so.1.0.0*
        libxenstat.so.0 -> libxenstat.so.0.0*
        libxenstore.so.3.0 -> libxenstore.so.3.0.1*
        libxenvchan.so.1.0 -> libxenvchan.so.1.0.0*
        libxlutil.so.1.0 -> libxlutil.so.1.0.0*
    and perhaps various usr/lib/fs/*, and ocaml and python modules.

    I don't think we've changed libxenstore incompatibly.  The others
    are sufficiently internal or unchanged that we are content ?

 * change xen-unstable README

    Seems to have 4.2 in it already.

 * change xen-unstable Config

    I can't see what this might refer to.  Config.mk doesn't seem
    to have a version number in it.

 * change xen-unstable xen/Makefile XEN_EXTRAVERSION

    I guess this will happen when we do the rc ?

And it's RC1 we're doing I guess, not RC0 ?  If so I will tag that in
the qemu trees.


Xen-devel mailing list



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