public inbox for
 help / color / mirror / Atom feed
From: John Dallaway <>
To: eCos Maintainers <>
Subject: Re: Bug crunching
Date: Fri, 27 Feb 2009 10:08:00 -0000	[thread overview]
Message-ID: <> (raw)

eCos maintainers

There are a number of bugs reported against eCos 3.0 beta 1 which are
still in the NEW state - the default assignee has not accepted the bug.
See the URL in my earlier mail (appended) and add the "Status" column to
your customised view of the bug list if necessary.

We need to form a view as to which of these bugs are important for eCos
3.0 and ensure that someone is assigned to fix the important ones. One
or two of the bugs have already been marked as non-blocking for eCos 3.0
which is fine.

In some of these cases it may be that the default assignee is not the
most appropriate person to look at the bug. If you are the default
assignee for one of these bugs, can you please indicate whether or not
you are intending to look at the bug for eCos 3.0 either by accepting
the bug (changing the state to ASSIGNED) or by adding some comment that
the bug is not important and/or someone else should look at it.

I'm particularly concerned about the POSIX test issues since POSIX
compatibility is an important feature.

Thank you

John Dallaway

-------- Original Message --------
Subject: Bug crunching
Date: Sun, 22 Feb 2009 15:11:21 +0000
From: John Dallaway <>

eCos maintainers

We already have several bug reports against eCos 3.0 beta 1:

I'm not complaining. The whole point of the beta period is to find and
eradicate bugs.

It would be helpful to share the load of processing these bugs as far as
possible. Could I therefore suggest that we all subscribe to the
"ecos-bugs" list on so that we are made aware of new bugs
as they arrive and can contribute where appropriate. Subscribing is
easily achieved using the mailing list request form:

Thank you

John Dallaway

             reply	other threads:[~2009-02-27 10:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 10:08 John Dallaway [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-22 15:11 John Dallaway

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