|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Time for 4.2.0 rc0?
Ian Campbell writes ("Re: [Xen-devel] Time for 4.2.0 rc0?"):
> [changelogs]
Oh thanks for digging into that.
> Parts of tools/blktap2.
>
> 24800:acf4ad70c87b "blktap2/libvhd: Build shared objects using -fPIC"
> might be interesting?
That's not an ABI change either. It might warrant a minor bump.
> 23055:a73a35527763 "tools: link each shared library or binary only
> against the libraries it uses" might be an ABI visible change?
No, I don't think it is.
> > libxenstore.so.3.0 -> libxenstore.so.3.0.1*
>
> tools/xenstore contains 24376:32a3d86ae4a4
> "libxenstore: Provide xs_check_watch" and 24507:19a0a2e26137 "xenstore:
> New function xs_path_is_subpath"
That warrants a minor bump, surely ? But not a soname change. Ie it
should be 3.0.2.
> > libxlutil.so.1.0 -> libxlutil.so.1.0.0*
>
> 23619:77a235e95b47 "libxl: disks: new xlu_disk_parse function"
Again I think that should be 1.0.1 then.
> Looks like we wanht to bump libxenstore and libxlu.
I agree.
> Possibly the blktap2 ones too, but they are pretty internal I guess.
Right.
> > * 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.
>
> Don't we switch QEMU_TAG to point to the tagged name instead of a SHA
> sum?
Yes. Perhaps that's what that means...
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |