public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marc G. Fournier <[email protected]>
To: Stefan Kaltenbrunner <[email protected]>
To: Dave Page <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Feature freeze progress report
Date: Sun, 29 Apr 2007 18:15:11 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- --On Sunday, April 29, 2007 21:30:36 +0200 Stefan Kaltenbrunner
<[email protected]> wrote:
> not sure I fully agree here - I think we could do a bit better on the
> "bug tracking front" but it is a bit unclear if we cn honestly sy that
> "the current process" does not work or is not going to scale in the
> future. Complex patches need time - sometimes much more time than a
> release or even two release cycles - it's unclear if trying to get those
> in more agressively (by having more commiters or applying them earlier)
> might not actually cause more harm due to -HEAD getting less stable and
> causing developers to spend time hunting regressions.
re: -HEAD getting less stable ... we wouldn't be adding just anyone as a
committer, only those that are trusted to know what they are doing ... even
'slapping in a patch', I would expect it to have some sort of preliminary
review by *someone* with a bit of knowledge in that aspect of the code ...
- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [email protected] MSN . [email protected]
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFGNQrf4QvfyHIvDvMRAoUqAKDKZY8rThsQi1vTKeQgq/c4HPIyzQCfe9o2
2fHy763eMw/hxGrMnDwXnLM=
=g6E8
-----END PGP SIGNATURE-----
view thread (98+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Feature freeze progress report
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox