From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6638 invoked by alias); 22 Jul 2006 17:40:43 -0000 Received: (qmail 6622 invoked by uid 22791); 22 Jul 2006 17:40:42 -0000 X-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from ascomax.hasler.ascom.ch (HELO ascomax.hasler.ascom.ch) (139.79.135.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 22 Jul 2006 17:40:40 +0000 Received: from eiger.ma.tech.ascom.ch (eiger.ma.tech.ascom.ch [139.79.100.1]) by ascomax.hasler.ascom.ch (8.12.9-20030924/8.12.9) with ESMTP id k6MHdbw0001312; Sat, 22 Jul 2006 19:39:47 +0200 (MEST) Received: from [139.79.100.143] (helo=donkey.ma.tech.ascom.ch) by eiger.ma.tech.ascom.ch with esmtp (Exim 3.16 #1) id 1G4LRu-0001Vp-00; Sat, 22 Jul 2006 19:39:34 +0200 Received: from lunn by donkey.ma.tech.ascom.ch with local (Exim 3.36 #1 (Debian)) id 1G4LRu-0006ZH-00; Sat, 22 Jul 2006 19:39:34 +0200 Date: Sat, 22 Jul 2006 17:40:00 -0000 To: Jonathan Larmour Cc: Gary Thomas , eCos Maintainers Subject: Re: Deprecating eCos 2.0 Message-ID: <20060722173934.GA25013@donkey.ma.tech.ascom.ch> References: <44B50114.6070004@mlbassoc.com> <44B50F45.3040904@jifvik.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B50F45.3040904@jifvik.org> User-Agent: Mutt/1.5.11+cvs20060403 From: Andrew Lunn 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/msg00002.txt.bz2 On Wed, Jul 12, 2006 at 04:03:33PM +0100, Jonathan Larmour wrote: > Gary Thomas wrote: > >Can we make the automated download tool (ecos-install.tcl) use > >a CVS snapshot instead of the old 2.0? It would solve so many > >"I'm using 2.0 ..." issues if this was the default. > > > >Note: I don't care if it still downloads the old tools (which > >are also labeled 2.0) as for the most part, they don't get > >in the way. > > It's certainly possible. Not a great message in one sense, but it would do > the job for now. Despite not much in the way of QA, it's arguably less > relevant to commend 2.0. > > But if we did, it would still want a version number distinct from true CVS, > i.e. instead of "current" for packages. Perhaps something like 2.1a-cvs or > 2.1a-interim? We'd also need a doc rebuild to make sense. Similarly what > about the prebuilt configtool and ecosconfig? The only prebuilt versions > that work with cygwin are on ecoscentric's site. > > So even a quicky respin isn't quite trivial but it wouldn't take long. Not > something to announce with a fanfare though. We always seem to run into these problems a while after a release. We should think forward for the next release. Do we really want to make a release with a different version number in the tree? 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. Andrew