From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14256 invoked by alias); 25 May 2005 14:56:44 -0000 Mailing-List: contact ecos-devel-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@sources.redhat.com Received: (qmail 14241 invoked by uid 22791); 25 May 2005 14:56:36 -0000 Received: from norbert.ecoscentric.com (HELO smtp.ecoscentric.com) (194.153.168.165) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 25 May 2005 14:56:36 +0000 Received: by smtp.ecoscentric.com (Postfix, from userid 99) id A416B65C086; Wed, 25 May 2005 15:56:34 +0100 (BST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by smtp.ecoscentric.com (Postfix) with ESMTP id 5DB2665C064; Wed, 25 May 2005 15:56:33 +0100 (BST) Message-ID: <42949221.3070009@jifvik.org> Date: Wed, 25 May 2005 14:56:00 -0000 From: Jonathan Larmour User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Korsgaard Cc: ecos-devel@ecos.sourceware.org Subject: Re: New release? References: <87acmnw8ht.fsf@p4.48ers.dk> In-Reply-To: <87acmnw8ht.fsf@p4.48ers.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on norbert.ecoscentric.com X-Spam-Level: X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-SW-Source: 2005-05/txt/msg00016.txt.bz2 Peter Korsgaard wrote: > Hi, > > As the eCos 2.0 release is turning 2 years this weekend > (http://ecos.sourceware.org/ml/ecos-announce/2003/msg00005.html), I > was wondering if it wasn't about time with a new release? It is indeed. > A new release would give some nice publicity and hopefully stop people > from wasting time on the ancient v2.0 release, only to later discover > that it was fixed long time ago in CVS. > > But what is the status? > > It would be nice if the Redhat->FSF assignment could be completed > before the release, but that doesn't seem to be happening? This is the main obstacle at this time, and is a prerequisite. All the maintainers are impatient about getting this resolved. It has in fact been partially resolved, and what's left to do is (to me) pretty clear and straightforward. But it has been very difficult to get a dialogue going at all, nevermind momentum. But your mail has been a worthwhile reminder for me to prod people to usher the process along, so I've now done so. > What about the flash v2 API? Is that getting ready for public > consumption? I imagine the push towards eCos 2.1/3.0/whatever will be the time that gets integrated. > * NET: SNTP, PPP, Improved IPv6 support, IPSEC, LwIP, VNC Fair enough, although I don't recall anything significant for IPv5, and IPsec was IIRC more a framework to allow future solutions, than a complete solution. Still, more than enough to justify a new release, probably a 3.0 to reflect the new IP status. There will be a lot of work before a 3.0 can happen though, even after the assignment. Jifl -- --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine