public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: v2.0 beta branch
Date: Fri, 14 Feb 2003 16:20:00 -0000	[thread overview]
Message-ID: <3E4D1748.60006@eCosCentric.com> (raw)
In-Reply-To: <1045237872.3771.167.camel@hermes.chez-thomas.org>

Gary Thomas wrote:
> On Fri, 2003-02-14 at 08:46, Jonathan Larmour wrote:
> 
>>Hi guys,
>>
>>We're now at the stage where we want to make a 2.0 beta branch in the 
>>public repository. Is everyone okay with that? This is just a branch in 
>>advance of the proper beta release so we can make sure it's a stable base 
>>for testing and generating the beta.
>>
>>If there are no objections I'll do it later this evening.
> 
> 
> Can you set a specific time for this?  I'd like to see if I can have 
> a new [platform] port ready before that.  n.b. it's pretty much ready
> now, I was just going to do a few tweaks before submitting.

Let's say 19:30 GMT. Jld wants to do some testing over the weekend, and 
wants to get it started this evening.

> If I miss this "deadline", it's no big deal, but it would be nice
> to get in under the wire.

I think we'll have to move to an "approve before commits" system pretty 
much straight away for anything but trivial bug fixes. So commit to the 
trunk when you're ready, post the patch, and $SOMEONEELSE can decide if 
it's safe or not.

At a guess, if it's very self-contained it's probably ok; if it plays 
around in arch/variant HALs for example, then probably not. So if it's the 
latter, it may not be worth busting a gut.

It'll probably be okay to relax the branch commit requirements a bit once 
the beta release is actually spun from the branch and available for 
download, just to make life easier for the beta period before the final.

This is only for target code of course, not docs etc.

>>Separately, but relevant before the branch, I and the other guys think 
>>it's about time we renamed the net template to old_net and new_net to net. 
>>Is this okay too? Obviously we'll update the docs with that.
> 
> 
> When you do that (it's OK by me), remember to point out that SNMP is
> not net working/available with the new stack.

Yep. And will do the CDL requires which seals it :-).

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

  parent reply	other threads:[~2003-02-14 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14 15:46 Jonathan Larmour
2003-02-14 15:51 ` Gary Thomas
2003-02-14 15:55   ` Andrew Lunn
2003-02-14 15:58     ` Gary Thomas
2003-02-14 16:00       ` Andrew Lunn
2003-02-14 16:02     ` Jonathan Larmour
2003-02-14 16:20   ` Jonathan Larmour [this message]
2003-02-14 16:24     ` Gary Thomas
2003-02-14 18:54     ` Jonathan Larmour
2003-02-14 19:09       ` Gary Thomas
2003-02-14 19:18         ` Jonathan Larmour
2003-02-14 19:20           ` Gary Thomas

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=3E4D1748.60006@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=gary@mlbassoc.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).