[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Next release
From: |
Adam Fedor |
Subject: |
Re: Next release |
Date: |
Thu, 17 Mar 2005 13:34:03 -0700 |
On Mar 17, 2005, at 8:13 AM, Adrian Robert wrote:
It's probably not necessary to burden "core developers" with these
tasks if others are willing to help out. There are some people who do
a lot of coding in base and gui and tend to give advice on patches and
the like. If any of them want to serve as release manager for base,
gui, or back then that's great. But it if not, that's great too, as
long as they can coordinate with someone else who handles the
mechanics of managing bug reports, doing stabilization branches, etc..
In this model, the release manager gets advice on technical issues
and good time points for releases from the technical folks, who go on
concentrating on coding and reviewing patches.
Communications are important -- this would only work if there were
specific designated people the release manager could contact with
questions and who are committed to helping them with decisions.
If this could be set up, then it might also be possible to consider
some kind of regularized release schedule, which might help people
delivering apps, packaging for distributions, etc..
Sounds like a good idea. We could use someone who is only moderately
familiar with the libraries to collect suggestions and draw up a
release plan