On Sat, Sep 02, 2006 at 06:31:51PM +0100, Dave Page wrote:
BTW, another output thing you might consider is having draft release
notes ready-to-go on demand. Currently, Bruce prepares the release
notes on the basis of a very tedious scan of the CVS commit logs.
If this sort of stuff were
On Sun, Sep 03, 2006 at 09:18:00AM +0200, Peter Eisentraut wrote:
Joshua D. Drake wrote:
http://pgbugs.commandprompt.com (still need to configure email).
Thank you for that.
I think an issue tracking system for patches and such may need to be
distinct from a bug-tracking system such as
Bruce Momjian wrote:
Robert Treat wrote:
FWIW I have never understood why we don't require patch submitters/committers
to update the release notes when they do the patch.
I've suggested this more than once in the past -- I think it would be a
clear improvement over the status quo. Updating
Right now, the release notes show a list of all the significant
items in each release, but it isn't available until the release,
and it isn't complete (because it would be unreadable by ordinary
users). And there is no tracking of individual items in progress
except by individual developers.
Joshua D. Drake wrote:
http://pgbugs.commandprompt.com (still need to configure email).
Thank you for that.
I think an issue tracking system for patches and such may need to be
distinct from a bug-tracking system such as bugzilla, but let's get one
thing after another up.
--
Peter
Peter Eisentraut wrote:
Joshua D. Drake wrote:
http://pgbugs.commandprompt.com (still need to configure email).
Thank you for that.
I think an issue tracking system for patches and such may need to be
distinct from a bug-tracking system such as bugzilla, but let's get one
thing after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane sagely noted:
No bug/issue tracker, or anything else, is going to be successful unless
somebody commits enough time to make it so. I've noted a whole lot of
enthusiasm for having a tracker in these recent discussions, but a
remarkable
Greg Sabino Mullane [EMAIL PROTECTED] writes:
I've been thinking about this a lot since before the Summit, and the
only solution I see is to design something specifically for us.
Well, nobody's going to accuse you of thinking too small ;-). Sounds
great to me, though, if you think you can pull
On Saturday 02 September 2006 11:42, Tom Lane wrote:
BTW, another output thing you might consider is having draft release
notes ready-to-go on demand. Currently, Bruce prepares the release
notes on the basis of a very tedious scan of the CVS commit logs.
If this sort of stuff were being
Tom Lane wrote:
Greg Sabino Mullane [EMAIL PROTECTED] writes:
I've been thinking about this a lot since before the Summit, and the
only solution I see is to design something specifically for us.
Well, nobody's going to accuse you of thinking too small ;-). Sounds
great to me, though, if
Robert Treat wrote:
On Saturday 02 September 2006 11:42, Tom Lane wrote:
BTW, another output thing you might consider is having draft release
notes ready-to-go on demand. Currently, Bruce prepares the release
notes on the basis of a very tedious scan of the CVS commit logs.
If this sort
Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane sagely noted:
No bug/issue tracker, or anything else, is going to be successful unless
somebody commits enough time to make it so. I've noted a whole lot of
enthusiasm for having a tracker in these recent
Greg Sabino Mullane wrote:
Yes, maintaining it will be a royal pain in the butt. But my theory has
been if you build it, they will come. It will require a lot of human
interaction, as automation only takes you so far, especially when trying
to parse mailing list messages. But if we eventually
Greg Sabino Mullane wrote:
There are a number of reasons for this, not least of which is the
enormous and ever-changing requirements such a system would have to
have.
The buildfarm is an excellent example of this.
The build farm is not an example of this. There isn't any build-farm
Greg Sabino Mullane wrote:
I've been thinking about this a lot since before the Summit, and the
only solution I see is to design something specifically for us.
Rather than get bogged down in details about how it will work and
what technologies it will be using, I'd like to share my ideas on
On 2/9/06 16:42, Tom Lane [EMAIL PROTECTED] wrote:
BTW, another output thing you might consider is having draft release
notes ready-to-go on demand. Currently, Bruce prepares the release
notes on the basis of a very tedious scan of the CVS commit logs.
If this sort of stuff were being
Peter Eisentraut wrote:
Greg Sabino Mullane wrote:
There are a number of reasons for this, not least of which is the
enormous and ever-changing requirements such a system would have to
have.
The buildfarm is an excellent example of this.
The build farm is not an example
Andrew Dunstan wrote:
Peter Eisentraut wrote:
Greg Sabino Mullane wrote:
There are a number of reasons for this, not least of which is the
enormous and ever-changing requirements such a system would have to
have.
The buildfarm is an excellent example of this.
The build
18 matches
Mail list logo