From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14091 invoked by alias); 30 Jan 2009 01:21:08 -0000 Received: (qmail 14083 invoked by uid 22791); 30 Jan 2009 01:21:07 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 30 Jan 2009 01:21:03 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id E0D553B4003F; Fri, 30 Jan 2009 01:21:00 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DHEmdfsvg4HP; Fri, 30 Jan 2009 01:20:59 +0000 (GMT) Message-ID: <49825601.5080505@eCosCentric.com> Date: Fri, 30 Jan 2009 01:21:00 -0000 From: Jonathan Larmour User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc3.4.legacy (X11/20060515) MIME-Version: 1.0 To: John Dallaway CC: ecos-maintainers@ecos.sourceware.org Subject: Re: Repository copyrights updated References: <4981EC0D.2050305@eCosCentric.com> <4982305F.8040503@dallaway.org.uk> In-Reply-To: <4982305F.8040503@dallaway.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org X-SW-Source: 2009-01/txt/msg00032.txt.bz2 John Dallaway wrote: > >>After the trunk is unfrozen, there will be a short time to commit anything >>important > > It will certainly be worthwhile fixing up the SH3 .ldi files before the > branch is cut. There is also a problem with linking the cxxsupp test for > ARM targets which are still using arm-elf-gcc 3.2.1. I also have a note of a number of other issues, such as i386 and mips linking, and a m68k compiler problem which may result in a workaround in the sources, off the top of my head (I'm sure there are others). Not that everything is frozen in the branch before it's cut of course, but it's helpful to avoid double commits. As well as patches, I will also be working on website updates as one of my highest priorities. There's a lot I need to do there, although that's aimed more at the final than the release candidate of course. Although an unstated assumption I want to make explicit is that I want the eCos 3.0 release to be shoved out without _too_ much angst about what needs to go in - people coming up with last minute contribs of new ports they want to go in for example shouldn't hold up the process. Let's just get it out there, because once it is, things will become easier and we can start thinking about consolidating stuff (and switching VCS, and etc.etc.), and are more likely to get assistance from the community in doing so. >>and then I will cut a branch for the eCos 3.0 release and then I >>will create a first release candidate - there will probably/hopefully only >>be one. > > > Are you referring to the repository tagging? For avoidance of doubt, I > will be generating the actual releases. Sorry, I didn't know you had made scripts for generating releases. As you know, eCosCentric aren't in a position to check-in ours, so I think it would be good if you could check in yours (any time after code thaw) for future release reproduction - I recommend a "release" module (not under ecos, but as a separate CVS module). And of course once your assignment is executed. Have you heard anything? I haven't been notified (yet). I would prefer to choose the timing of the repo tag'n'branch myself, in which case I may as well actually do it (and let you know at that point). > I have everything set up for > this on my release machines. Hence my earlier request for shell access > to sourceware.org for uploading of the releases. FAOD, the maintainers as a group need to be happy with the state of the release before it goes up for download. NB I have added the version '3.0rc1' to bugzilla. The b suffix used for 2.0 confused people if you remember, and that seems to be the most common nomenclature now anyway. Jifl -- eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. ------["The best things in life aren't things."]------ Opinions==mine