public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: ecos-maintainers@ecos.sourceware.org
Subject: Re: ecos-v3_0-branch
Date: Sun, 22 Feb 2009 09:17:00 -0000	[thread overview]
Message-ID: <49A11817.6070006@dallaway.org.uk> (raw)
In-Reply-To: <499E7AAD.5070501@dallaway.org.uk>

eCos maintainers

eCos 3.0 beta 1 is out. Many thanks to everyone who helped with this in
one way or another. Of course, our job is not yet complete. Please do
volunteer to test the beta release on the targets you have to hand and
therefore encourage the wider eCos community to do likewise.

John Dallaway wrote:

> The ecos-v3_0-branch has now been created and is currently frozen for
> 3.0 beta 1 release engineering. Feel free to resume check-ins on the trunk.

The ecos-v3_0-branch is now tagged and unfrozen. However, please limit
changes on this branch to patches which directly address issues in the
eCos 3.0 beta 1 release.

It would be helpful to ensure that a Bugzilla issue is raised (version
== "3.0beta1") for each patch so we can readily review what has been
fixed and what is outstanding.

I will add some extra components in Bugzilla for the new infrastructure
packages. Do we really need to split out documentation into separate
Bugzilla components? Of course, if we did this consistently it would
double the number of Bugzilla components.

John Dallaway

  reply	other threads:[~2009-02-22  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  9:41 ecos-v3_0-branch John Dallaway
2009-02-22  9:17 ` John Dallaway [this message]
2009-02-22 21:29   ` ecos-v3_0-branch Jonathan Larmour

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=49A11817.6070006@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-maintainers@ecos.sourceware.org \
    /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).