public inbox for
 help / color / mirror / Atom feed
From: John Dallaway <>
Subject: Re: Deprecating eCos 2.0
Date: Mon, 24 Jul 2006 17:58:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

  reply	other threads:[~2006-07-24 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 14:03 Gary Thomas
2006-07-12 15:03 ` Jonathan Larmour
2006-07-22 17:40   ` Andrew Lunn
2006-07-22 22:52     ` Jonathan Larmour
2006-07-24 17:58       ` John Dallaway [this message]
2006-07-31  8:43         ` Andrew Lunn

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:

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

  git send-email \ \ \ \

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