From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
Subject: Re: [Xen-users] Re: Xen document day (Oct 12 or 26)
Date: Sun, 2 Oct 2011 14:12:16 +0300
Message-ID: <20111002111216.GA12984@reaktio.net>
References: <20110922130618.GA13238@phenom.oracle.com>
	<20110929141317.GX12984@reaktio.net>
	<CAOzFzEieWhgoBWEXQFjqr8PYoVOAcU20rtA2Q3OhyA+=dD9Atg@mail.gmail.com>
	<4E85A9B7.7040605@xen.org>
	<CAFivhPnc-Mpv+Yapp3fVkV2awDcfGw0nv_gWERftnLJXA0_M5A@mail.gmail.com>
	<20110930235247.GY12984@reaktio.net>
	<CAFivhPkm7FU7Qp9r2oYB2UYRQiZBpHHqVQ8QNB9MDqWbBjBQwg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <CAFivhPkm7FU7Qp9r2oYB2UYRQiZBpHHqVQ8QNB9MDqWbBjBQwg@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Florian Heigl <florian.heigl@gmail.com>
Cc: Joseph Glanville <joseph.glanville@orionvm.com.au>, Lars Kurth <lars.kurth@xen.org>, xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, xen-users@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Sat, Oct 01, 2011 at 08:06:09PM +0200, Florian Heigl wrote:
> 2011/10/1 Pasi Kärkkäinen <pasik@iki.fi>:
> > On Fri, Sep 30, 2011 at 06:33:40PM +0200, Florian Heigl wrote:
> >> 2011/9/30 Lars Kurth <lars.kurth@xen.org>:
> >> > 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