From: Stan Shebs <shebs@apple.com>
To: gdb@sources.redhat.com
Subject: Call for volunteers - GDB Release Manager
Date: Fri, 02 Sep 2005 22:28:00 -0000 [thread overview]
Message-ID: <4318D1E8.6060805@apple.com> (raw)
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
reply other threads:[~2005-09-02 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4318D1E8.6060805@apple.com \
--to=shebs@apple.com \
--cc=gdb@sources.redhat.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).