public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Chris Zimman <czimman@bloomberg.com>
Cc: Frank Pagliughi <fpagliughi@mindspring.com>,
		ecos-discuss@sources.redhat.com
Subject: Re: [ECOS]  Re: Is eCos project still alive?
Date: Fri, 14 Dec 2007 11:20:00 -0000	[thread overview]
Message-ID: <20071214104551.GD13033@lunn.ch> (raw)
In-Reply-To: <F31C1582037F5041B0CD525FD870AE6A063801@ny2545.corp.bloomberg.com>

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....

      Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-12-14 10:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  9:46 Loginov Alexander
2007-12-13  9:50 ` Loginov Alexander
2007-12-13 15:15 ` Grant Edwards
2007-12-13 15:43   ` Chris Zimman
2007-12-13 17:40     ` Grant Edwards
2007-12-14  0:48       ` Bob Koninckx
2007-12-14  1:41         ` Grant Edwards
2007-12-14  6:38           ` Frank Pagliughi
2007-12-14 11:15             ` Chris Zimman
2007-12-14 11:20               ` Andrew Lunn [this message]
2007-12-14 12:00                 ` Paul D. DeRocco
2007-12-14 14:28                 ` [ECOS] FSF copyright assignmnett. [Was Re: [ECOS] Re: Is eCos project still alive?] Ilija Koco
2007-12-14 16:21                   ` [ECOS] FSF copyright assignment. " Daniel Morris
2007-12-14 17:11                 ` [ECOS] Re: Is eCos project still alive? Grant Edwards
2007-12-14 18:10                   ` Brian Austin
2007-12-17 11:29                 ` Jonathan Larmour
2007-12-14 16:34             ` Brian Austin
2007-12-14 16:39               ` Sergei Organov
2007-12-14 18:47               ` Grant Edwards
2007-12-13 20:06 ` Mike Arthur
2007-12-14 13:47 ` Ilija Koco
  -- strict thread matches above, loose matches on Subject: below --
2007-12-14  9:07 Loginov Alexander
2007-12-14  8:28 Loginov Alexander
2007-12-14 11:09 ` Chris Zimman
2007-12-13  4:27 [ECOS] " Loginov Alexander
2007-12-13  6:15 ` [ECOS] " Grant Edwards
2007-12-13  3:31 Loginov Alexander
2007-12-13  8:07 ` Grant Edwards
2007-12-13 15:08   ` Brian Austin
2007-12-13  3:02 Anthony Tonizzo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071214104551.GD13033@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=czimman@bloomberg.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=fpagliughi@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).