From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3285 invoked by alias); 2 Sep 2005 22:28:09 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3186 invoked by uid 22791); 2 Sep 2005 22:28:01 -0000 Received: from mail-out4.apple.com (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 02 Sep 2005 22:28:01 +0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id j82MRxEM025143 for ; Fri, 2 Sep 2005 15:27:59 -0700 (PDT) Received: from relay3.apple.com (relay3.apple.com [17.128.113.33]) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.17) with ESMTP id for ; Fri, 2 Sep 2005 15:27:59 -0700 Received: from [17.219.197.111] ([17.219.197.111]) by relay3.apple.com (8.12.11/8.12.11) with ESMTP id j82MRwvO019168 for ; Fri, 2 Sep 2005 15:27:58 -0700 (PDT) Message-ID: <4318D1E8.6060805@apple.com> Date: Fri, 02 Sep 2005 22:28:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Call for volunteers - GDB Release Manager Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-09/txt/msg00018.txt.bz2 For several years, Andrew Cagney has been ably serving as GDB's release manager in addition to his general maintainer role, but has now stepped back, to let somebody else have some of the fun. The Steering Committee has decided to give everybody a crack at the job by soliciting volunteers. Here is the formal description of the role: * The GDB Steering Committee appoints a Release Manager. * The Release Manager is responsible for organizing, scheduling, and managing releases of GDB. * The Release Manager decides the approval and commit policies for release branches, and can change them as needed. * The release manager can resign at any time. The Steering Committee will appoint a replacement in a reasonable amount of time. * The Steering Committee retains the authority to overrule or replace the Release Manager, but will not ordinarily do so. What does all this mean? In my view, being a release manager is a great way to get more involved with GDB without having to be an oldtime hacker who knows every minute detail of call frames on hppa or what dve3900-rom.c is supposed to be for. You get the latitude to decide when a new version of GDB is good enough to be unleashed on the world, which in turn becomes the debugger shipped with GNU/Linux, *BSD, and other operating systems (a good thing for the resume!) At the same time, you get to make the calls on whether to fix tough bugs or let them go, though you'll get plenty of advice from everybody else. :-) It's important to be comfortable with CVS and net-based collaboration, and good to have touches of both diplomatic and nagging skills. If you're interested, we'd like to hear from you! You can either volunteer publicly on this list, or send private mail to any SC person (as listed on http://sourceware.org/gdb/committee). We haven't set a fixed period to take names, but it's getting to be time to start thinking about the next release, so the sooner you get your name in, the sooner you can start making it happen. Stan