From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19011 invoked by alias); 18 Mar 2003 22:58:01 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 18836 invoked from network); 18 Mar 2003 22:57:59 -0000 Message-ID: <3E77A421.8010209@eCosCentric.com> Date: Tue, 18 Mar 2003 22:58:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.2) Gecko/20021203 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Andrew Lunn Cc: ecos-maintainers@sources.redhat.com Subject: Re: Proposal for processing patches for the eCos 2.0 branch References: <200303180848.24682.jld@ecoscentric.com> <1047995318.7459.2925.camel@hermes.chez-thomas.org> <200303181605.21189.jld@ecoscentric.com> <20030318190053.GF17373@biferten.ma.tech.ascom.ch> In-Reply-To: <20030318190053.GF17373@biferten.ma.tech.ascom.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00021.txt.bz2 Andrew Lunn wrote: > Hi folks > > Is there some sort of time plan for 2.0 final? The longer it takes, > the more patches from the trunk we will want to put into the branch. We were saying the same earlier over lunch :-). While the "official" answer to give the net is always "when it's ready" (although it never really will be, arguably), we should aim for a month or so - enough time for feedback, but not enough time for serious divergence. It's possible we can do some sort of rolling snapshot releases from the trunk, but the overhead and care and feeding may be too difficult, as well as the inevitable support questions (it can be _good_ to put the "barrier" of CVS in the way!). Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine