From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 839 invoked by alias); 24 Jul 2006 17:58:52 -0000 Received: (qmail 669 invoked by uid 22791); 24 Jul 2006 17:58:49 -0000 X-Spam-Status: No, hits=-0.6 required=5.0 tests=BAYES_20,FORGED_RCVD_HELO X-Spam-Check-By: sourceware.org Received: from mta09-winn.ispmail.ntl.com (HELO mtaout03-winn.ispmail.ntl.com) (81.103.221.49) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 24 Jul 2006 17:58:43 +0000 Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20060724175839.KLTA1865.mtaout03-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com> for ; Mon, 24 Jul 2006 18:58:39 +0100 Received: from wok.localdomain ([86.7.17.143]) by aamtaout02-winn.ispmail.ntl.com with ESMTP id <20060724175839.YPTU23938.aamtaout02-winn.ispmail.ntl.com@wok.localdomain> for ; Mon, 24 Jul 2006 18:58:39 +0100 Received: from [127.0.0.1] (wok.localdomain [127.0.0.1]) by wok.localdomain (8.13.7/8.13.4) with ESMTP id k6OHwaeB021000 for ; Mon, 24 Jul 2006 18:58:37 +0100 Message-ID: <44C50A4C.6090400@dallaway.org.uk> Date: Mon, 24 Jul 2006 17:58:00 -0000 From: John Dallaway User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ecos-maintainers@ecos.sourceware.org Subject: Re: Deprecating eCos 2.0 References: <44B50114.6070004@mlbassoc.com> <44B50F45.3040904@jifvik.org> <20060722173934.GA25013@donkey.ma.tech.ascom.ch> <44C2AC10.1030606@jifvik.org> In-Reply-To: <44C2AC10.1030606@jifvik.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org X-SW-Source: 2006-07/txt/msg00004.txt.bz2 Jonathan Larmour wrote: > Andrew Lunn wrote: > >> Wouldn't it be >> better to just make a snapshot of CVS, with the CVS directories, so >> that people can do a cvs up. Also change the documentation to >> encourage people to do this as the last part of the installation >> process. > > It's a dubious enough suggestion as it is to be making a release that > isn't stabilised (although at least we can fix up any real > showstoppers). Positively encouraging use of sources that can be > infrequently but occasionally seriously broken, seems even less wise. I agree with Jifl that we need a way to readily distinguish official releases from CVS checkouts. Official releases cater for a different class of user who cares more about stability than about the very latest features. Of course, we need to do what we can to ensure that the next official release lives up to such expectations. I would support retaining the "v2_x" style of version directories for future releases. Users always have the option of checking out a specific version of eCos from CVS using a release tag if they prefer a stable repository that can be updated in the future. John Dallaway