public inbox for
 help / color / mirror / Atom feed
From: Jonathan Larmour <>
To: Andrew Lunn <>
Cc: eCos Maintainers <>
Subject: Re: Deprecating eCos 2.0
Date: Sat, 22 Jul 2006 22:52:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Andrew Lunn wrote:
> We always seem to run into these problems a while after a release.

Well, we've only had one non-Red Hat 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?

I think so yes. Normally it's reasonable to assume that if people 
reporting problems have packages with v2_0 in the name, it's a giveaway 
that it's old; and if it's "current", then not only is it from cvs, but it 
is likely to be recent CVS (even the snapshots via FTP are updated weekly 
so people can easily keep up-to-date). If we ship out stuff with "current" 
in the package name, there will be a marked increase in people with paths 
saying "current" when actually it's out of date. We want to catch when 
people are using old sources, and it's not hard to achieve.

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

------["The best things in life aren't things."]------      Opinions==mine

  reply	other threads:[~2006-07-22 22:52 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 [this message]
2006-07-24 17:58       ` John Dallaway
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).