On 9 Dec 2002 at 11:38, Tom Lane wrote:
> "Dan Langille" <dan@langille.org> writes:
> > Let's create a release team. This strategy is one well established
> > in other projects and in industry. For lack of a better starting
> > reference, let me suggest http://www.freebsd.org/releng/charter.html
> > as a starting point for consideration. See also
> > http://www.freebsd.org/releng/index.html.
>
> > This will also lighten the load on the core team allowing them to
> > focus on development and such.
>
> I don't really see any value-added here. The core committee's only
> routinely-exercised function is to organize releases; separating that
> out would leave core with nothing to do.
So we already have a release team, but not titled as such.
> Also, to the extent that
> core has any real or perceived authority in the project, I think it
> comes from having control of the release process --- there's surely no
> other reason for people to defer to the core team as a group (as
> opposed to whatever respect might be accorded to individual people as
> a result of their individual contributions).
Is the process documented? Any set procedure? Who knows how to do
it?
> So ISTM such a
> reorganization would leave the core committee as a figurehead and make
> the release team into the effective new core.
Is 'core' the same as 'steering'? I couldn't find any reference to
"core committe" or "core team" via google. At
http://developer.postgresql.org/bios.php I see the group of people
referred to as "Steering". Is their function defined anywhere?
If these things are not documented, they should be. Where do I
start?
--
Dan Langille : http://www.langille.org/
