WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: [Xen-devel] Xen document day (Oct 12 or 26)

On Sat, Oct 01, 2011 at 08:06:09PM +0200, Florian Heigl wrote:
> 2011/10/1 Pasi Kärkkäinen <pasik@xxxxxx>:
> > On Fri, Sep 30, 2011 at 06:33:40PM +0200, Florian Heigl wrote:
> >> 2011/9/30 Lars Kurth <lars.kurth@xxxxxxx>:
> >> > Let me know, which date you agreed on. We could do a poll.
> >> > We should publish on the blog a bit before.
> >> > Also, how can I help?
> >>
> >> One thing where you could probably help best is setting clear rules
> >> what do document for a release.
> >> i.e. the 4.0 relnotes had build instructions and a lot more, whereas
> >> this is missing in the next release note.
> >>
> >> either the build instructions were in the wrong place for 4.0 or 4.1
> >> was released with incomplete info ;)
> >> making a checklist sounds *ahem* in place :)
> >>
> >
> > Xen 4.1 releasenotes do state that "check Xen 4.0 releasenotes for build 
> > instructions and more info" :)
> 
> You see how well that worked for me :)
> 
> Imagine a magazine which has half of the standard topics missing on
> it's second issue with a pointer to the last one.
> And tbh I guess if anyone had re-tested the 4.0 build instructions
> line by line and found them 100% working then he'd probably have
> copied them over?
> 

Well they ARE working, that's why I didn't copy them when I wrote 4.1 page :-)
But anyway, feel free to do that!

> Flo
> -- 
> the purpose of libvirt is to provide an abstraction layer hiding all
> xen features added since 2006 until they were finally understood and
> copied by the kvm devs.

:)

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>