From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH RFC 0/5] Split off mini-os to a separate tree Date: Tue, 27 Jan 2015 12:16:08 +0000 Message-ID: <1422360968.25294.12.camel@citrix.com> References: <1422209626-9926-1-git-send-email-wei.liu2@citrix.com> <20150125182511.GA24026@zion.uk.xensource.com> <93F1150D-07CA-4F4B-A3A5-49532FCC23FF@recoil.org> <20150127115206.GH24026@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150127115206.GH24026@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Thomas Leonard , Stefano Stabellini , Anil Madhavapeddy , Ian Jackson , xen-devel@lists.xen.org, pooka@iki.fi, quan.xu@intel.com, Samuel Thibault , dgdegra@tycho.nsa.gov List-Id: xen-devel@lists.xenproject.org On Tue, 2015-01-27 at 11:52 +0000, Wei Liu wrote: > Splitting should be done sooner in the release cycle rather than later > IMHO. I agree, it should be done very soon and we should avoid letting the perfect be the enemy of taking the first step (to mix a few idoims). > > What's the planned release schedule for the new MiniOS? Independent > > of Xen or initially coupled? > > > > My initial thought is that we should start coupled. Releasing > independently requires more man power than releasing coupled. Of course > the option to release independently is always available. I agree, lets take the first step and get it moved out but and then once things have been properly decoupled at the code level etc think about decoupling the release process too. Ian.