From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20092 invoked by alias); 14 Dec 2007 16:39:59 -0000 Received: (qmail 20083 invoked by uid 22791); 14 Dec 2007 16:39:59 -0000 X-Spam-Check-By: sourceware.org Received: from outbound-va3.frontbridge.com (HELO outbound6-va3-R.bigfish.com) (216.32.180.16) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Dec 2007 16:39:39 +0000 Received: from outbound6-va3.bigfish.com (localhost.localdomain [127.0.0.1]) by outbound6-va3-R.bigfish.com (Postfix) with ESMTP id 5CDF2C71789 for ; Fri, 14 Dec 2007 16:39:37 +0000 (UTC) Received: from mail83-va3-R.bigfish.com (si1-va3 [10.7.14.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by outbound6-va3.bigfish.com (Postfix) with ESMTP id 5B982650061 for ; Fri, 14 Dec 2007 16:39:37 +0000 (UTC) Received: from mail83-va3 (localhost.localdomain [127.0.0.1]) by mail83-va3-R.bigfish.com (Postfix) with ESMTP id 44A8DB601FA for ; Fri, 14 Dec 2007 16:39:37 +0000 (UTC) X-BigFish: VP X-MS-Exchange-Organization-Antispam-Report: OrigIP: 141.131.3.20;Service: EHS Received: by mail83-va3 (MessageSwitch) id 1197650377228224_27019; Fri, 14 Dec 2007 16:39:37 +0000 (UCT) Received: from mail1.cirrus.com (mail1.cirrus.com [141.131.3.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail83-va3.bigfish.com (Postfix) with ESMTP id 1D9C25C0076 for ; Fri, 14 Dec 2007 16:39:37 +0000 (UTC) Received: from CLMSG-01.ad.cirrus.com ([198.61.95.37]) by mail1.cirrus.com (8.12.11.20060308/8.12.11) with ESMTP id lBEGcqfk017336 for ; Fri, 14 Dec 2007 10:38:52 -0600 Received: from [198.61.92.105] ([198.61.92.105]) by CLMSG-01.ad.cirrus.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 14 Dec 2007 10:39:36 -0600 From: Brian Austin Cc: ecos-discuss@sources.redhat.com In-Reply-To: References: <1197567366.3593.17.camel@lucretius.esaturnus.com> <476190B4.2050606@mindspring.com> <20071214104551.GD13033@lunn.ch> Content-Type: text/plain Date: Fri, 14 Dec 2007 18:10:00 -0000 Message-Id: <1197650254.23339.36.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Re: Is eCos project still alive? X-SW-Source: 2007-12/txt/msg00091.txt.bz2 What does the ecos group wish to accomplish by making releases? If it causes people to not use it, then I guess I "release" with a more recent date could help that cause, but other than that, I see nothing wrong with just pulling the tips _if_ you need new code. I have not had people ask me for an official release though. As long as it does what it's supposed to, they dont seem to mind. my 2 cents. Brian On Fri, 2007-12-14 at 16:33 +0000, Grant Edwards wrote: > On 2007-12-14, Andrew Lunn wrote: > > On Fri, Dec 14, 2007 at 05:38:02AM -0500, Chris Zimman wrote: > >> Frank, > >> > >> I think you raise a valid point here. Perhaps it would be time to consider > >> creating a more up to date release. > >> Rather frequently on the list, someone will say something to the effect of > >> 'I've downloaded/am using eCos 2.0 ...blah blah...it seems very out of > >> date...' The traditional response has been 'Go pull the latest from CVS'. > >> > >> Thoughts anyone? > > > > It has been for a long time the aim to make a release once the > > copyright transfer to FSF is completed. This has take much > > much longer than we ever thought it would take. We are nearly > > there, there is just one copyright assignment left, which is > > taking a while to sort out. > > > > Once this is completed we will start the work needed for a > > release. This is not something we can do overnight. It > > involves a lot of work. Nearly ever file needs to be touched > > in order to change the copyright notices. We probably need new > > tool chains, want to merge in the v2 flash branch, maybe pick > > up some patches which got dropped along the way etc. We need > > to do a lot of testing.... > > If there's anything that can be done by soembody with a few > hours a week to spare, let us know. > > As far as testing goes, my opinion is that a "release" doesn't > have to be guaranteed 100% bug free. It would just need to > mean that there aren't any known incomatibilities beetween > major packages. I think what we need more than anything is > just some snaphosts that can be used as reference points when > discussing or documenting things. It's OK if release XYZ has > some bugs. The important thing is to be able to say "I'm > running release XYZ with these patches" and have that mean > something. > > I know one can accomplish the same thing by using a CVS > snapshot for a particular date/time, but without common > reference points in the development history, it's difficult to > even discuss some things. > > -- > Grant Edwards grante Yow! I'm gliding over a > at NUCLEAR WASTE DUMP near > visi.com ATLANTA, Georgia!! > > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss