On Aug 17, 2006, at 3:40 PM, Alvaro Herrera wrote:
The searching capabilities in debbugs are, well, non-existent,
which is
a real problem in my mind.
Well, we can set up our own indexing, like Oleg and Teodor have
done in
http://www.pgsql.ru/
That seems like quite a hack for something
On 8/17/06, Peter Eisentraut [EMAIL PROTECTED] wrote:
Alvaro Herrera wrote:
Have you tried to use debbugs?
If you can find up-to-date source code for debbugs, we might continue
that line of thought.
http://www.mail-archive.com/debian-debbugs@lists.debian.org/msg01266.html
( bzr get
Marko Kreen wrote:
On 8/17/06, Peter Eisentraut [EMAIL PROTECTED] wrote:
Alvaro Herrera wrote:
Have you tried to use debbugs?
If you can find up-to-date source code for debbugs, we might continue
that line of thought.
http://www.mail-archive.com/debian-debbugs@lists.debian.org/msg01266.html
Andrew,
Why are we even dabating a system when it has been reported that the
authors believe it is completely unsuitable for use by the PostgreSQL
project?
Not *completely*. More that it would take a couple dozen hours of work to
make it good for us, and the resulting version then couldn't
Josh Berkus josh@agliodbs.com writes:
On the other hand, a lot of my personal dislike of BugZilla seems to be
based on being forced to use old versions. A lot of the stuff I hate
about it has been fixed in the current version.
Does that include it being basically a web-only interface?
I expect if you set up a web-based interface it won't be a matter of people
digging in heels so much as just being indifferent to it. And like most
projects the bugs will just accumulate and not get feedback.
And which projects would these be? Oddly enough it might surprise you
that the
Gregory Stark [EMAIL PROTECTED] writes:
I'm listed on various mozilla bugs and occasionally get notifications of
updates but I can't reply to those notifications and I'm not about to fire up
a browser and log in and search for the bug just to add comments.
It's really not that painful: every
Gregory Stark wrote:
Josh Berkus josh@agliodbs.com writes:
On the other hand, a lot of my personal dislike of BugZilla seems to be
based on being forced to use old versions. A lot of the stuff I hate
about it has been fixed in the current version.
Does that include it being
Tom Lane wrote:
Gregory Stark [EMAIL PROTECTED] writes:
I'm listed on various mozilla bugs and occasionally get notifications of
updates but I can't reply to those notifications and I'm not about to fire up
a browser and log in and search for the bug just to add comments.
It's
I wrote:
I will check about Greg's complaint about race conditions in updating
comments. My initial impression is that this is no longer so, but I
will get a definite answer.
My impression was correct. Each comment on a bug gets its own row,
marked by bug-id, commenter-id and
On Thu, Aug 17, 2006 at 08:20:22PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Have you tried to use debbugs? I agree with Greg Stark that it's a
better fit for our current procedure, while enabling better
traceability.
The principal strike against debbugs seems to
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Have you tried to use debbugs? I agree with Greg Stark that it's a
better fit for our current procedure, while enabling better
traceability.
The principal strike against debbugs seems to be that the source code is
not readily
All,
I chatted some with some of the Debian folks who maintain Debbugs. They
thought it would take a significant amount of work to adapt it to
PostgreSQL, in addition to the obvious needs to improve the web interface.
RT has some significant short comings for our project such as not having
So, the question is whether any of our biggest bug-fixers would dig in
their heels and scream No! if we gave BugZilla a try. Comments?
I could have this setup this weekend should we vote YES :)
Joshua D. Drake
---(end of
Let me add that most entries that illict a quick patch or TODO item do
not come in through the bugs list, but are rather problems people post
to ther lists, or are the result of discussions.
---
Gregory Stark wrote:
Andrew
Greg,
In short, it's just a tool to solve a problem we actually have (having a
convenient archive of data about current and past bugs) without inventing
problems to solve with extra process that we aren't already doing anyways.
RT can be set up similarly but I'm not sure how much work it would
Josh Berkus schrieb:
Greg,
In short, it's just a tool to solve a problem we actually have (having a
convenient archive of data about current and past bugs) without inventing
problems to solve with extra process that we aren't already doing
anyways.
RT can be set up similarly but I'm not
I'm not sure I follow this, since currently anyone can
email the bugs
list or use the bugs - email form from the website. Are
you looking
to increase the barrier for bug reporting?
Any garbage (ie. spam) is generally filtered before it hits
the -bugs list itself
Spam: Yes.
On Thu, Aug 17, 2006 at 06:48:54PM +0200, Magnus Hagander wrote:
This, however, I would find very useful - both as a -hacker and as a
user. The point is that only confirmed things should be in there, so
only confirmed things should be returned on searches and whatevr.
(private not as in not
Magnus Hagander wrote:
I'm not sure I follow this, since currently anyone can
email the bugs
list or use the bugs - email form from the website. Are
you looking
to increase the barrier for bug reporting?
Any garbage (ie. spam) is generally filtered before it hits
the
These days I doubt there's anyone around the project who
refuses to use a web browser at all. However, I still
personally find it much more convenient to read and respond
to mailing-list postings than to have to go and visit random
web pages to find out if there's something I need to
This, however, I would find very useful - both as a -hacker
and as a
user. The point is that only confirmed things should be in
there, so
only confirmed things should be returned on searches and whatevr.
(private not as in not visible to the public, but private as in
On Wed, Aug 16, 2006 at 06:52:21AM +0200, Peter Eisentraut wrote:
Tom Lane wrote:
that the bug tracker would have to have a reasonable output email
capability, but I'd not necessarily insist on being able to input
to it by mail. Red Hat's present bugzilla system could be described
that
On Wed, Aug 16, 2006 at 01:22:43PM +0900, Michael Glaesemann wrote:
On Aug 16, 2006, at 12:29 , Tom Lane wrote:
So my current take on this would be that the bug tracker
would have to have a reasonable output email capability, but I'd not
necessarily insist on being able to input to it by
RT has an E-mail interface. That was one of our considerations
when we used it to replace our aging trouble ticket system. What
does the interface need to do? RT's is pretty flexible.
Ken
On Tue, Aug 15, 2006 at 04:59:46PM -0500, Jim C. Nasby wrote:
On Tue, Aug 15, 2006 at 10:53:28AM -0500,
On Thu, Aug 17, 2006 at 07:00:21PM +0200, Magnus Hagander wrote:
These days I doubt there's anyone around the project who
refuses to use a web browser at all. However, I still
personally find it much more convenient to read and respond
to mailing-list postings than to have to go and
On Thu, Aug 17, 2006 at 07:05:17PM +0200, Magnus Hagander wrote:
I've yet to see a bug tracker that doesn't make it trivial to
identify bugs that were marked as invalid (ie: not a real
bug). The only difference is that you actually have to mark
Well, if it's invalid, it shouldn't be in
Magnus Hagander [EMAIL PROTECTED] writes:
... Red Hat's present bugzilla system
could be described that way --- and while I can't say I'm in
love with it, I can deal with it.
Doesn't bugzilla insist on sending you the complete bug every time?
Nope, it just sends the changes/additions.
Jim C. Nasby wrote:
On Thu, Aug 17, 2006 at 07:05:17PM +0200, Magnus Hagander wrote:
I've yet to see a bug tracker that doesn't make it trivial to
identify bugs that were marked as invalid (ie: not a real
bug). The only difference is that you actually have to mark
Well, if it's
Tom Lane wrote:
Doesn't bugzilla insist on sending you the complete bug every time?
Nope, it just sends the changes/additions. Other than the lack of a
direct email input method, I find BZ quite usable. Josh was just
complaining that its source code is a mess (dunno, haven't looked)
but
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
... Red Hat's present bugzilla system
could be described that way --- and while I can't say I'm in
love with it, I can deal with it.
Doesn't bugzilla insist on sending you the complete bug every time?
Nope, it just sends
Alvaro Herrera wrote:
Have you tried to use debbugs?
If you can find up-to-date source code for debbugs, we might continue
that line of thought.
The searching capabilities in debbugs are, well, non-existent, which is
a real problem in my mind.
--
Peter Eisentraut
Peter Eisentraut wrote:
Alvaro Herrera wrote:
Have you tried to use debbugs?
If you can find up-to-date source code for debbugs, we might continue
that line of thought.
Josh Berkus said he'd try to talk to the Debian people at LinuxWorld --
let's see if something materializes from there.
Alvaro Herrera [EMAIL PROTECTED] writes:
Have you tried to use debbugs? I agree with Greg Stark that it's a
better fit for our current procedure, while enabling better
traceability.
The principal strike against debbugs seems to be that the source code is
not readily available and/or isn't
Am Mittwoch, 16. August 2006 14:10 schrieb Robert Treat:
I'm not sure I follow this, since currently anyone can email the bugs list
or use the bugs - email form from the website. Are you looking to
increase the barrier for bug reporting?
Only a small fraction of the new posts on pgsql-bugs
On Wednesday 16 August 2006 00:52, Peter Eisentraut wrote:
Tom Lane wrote:
that the bug tracker would have to have a reasonable output email
capability, but I'd not necessarily insist on being able to input
to it by mail. Red Hat's present bugzilla system could be described
that way ---
On Wed, Aug 16, 2006 at 02:28:53PM +0200, Peter Eisentraut wrote:
Am Mittwoch, 16. August 2006 14:10 schrieb Robert Treat:
I'm not sure I follow this, since currently anyone can email the bugs list
or use the bugs - email form from the website. Are you looking to
increase the barrier for
Martijn van Oosterhout wrote:
On Wed, Aug 16, 2006 at 02:28:53PM +0200, Peter Eisentraut wrote:
Am Mittwoch, 16. August 2006 14:10 schrieb Robert Treat:
I'm not sure I follow this, since currently anyone can email the bugs list
or use the bugs - email form from the website. Are you
On Wed, Aug 16, 2006 at 09:14:47AM -0400, Andrew Dunstan wrote:
What we are talking about here is bug triage. Weeding out misreports,
duplicates etc. is a prime part of this function. It is essential to the
health of any functioning bug tracking system. All it takes is
resources. Is it
On Tue, Aug 15, 2006 at 10:43:12PM -0700, Josh Berkus wrote:
Tom,
These days I doubt there's anyone around the project who refuses to use
a web browser at all. However, I still personally find it much more
convenient to read and respond to mailing-list postings than to have to
go and
Jim C. Nasby wrote:
On Tue, Aug 15, 2006 at 10:43:12PM -0700, Josh Berkus wrote:
Tom,
These days I doubt there's anyone around the project who refuses to use
a web browser at all. However, I still personally find it much more
convenient to read and respond to mailing-list postings
On Wed, 16 Aug 2006, Robert Treat wrote:
I'm not sure I follow this, since currently anyone can email the bugs
list or use the bugs - email form from the website. Are you looking to
increase the barrier for bug reporting?
Any garbage (ie. spam) is generally filtered before it hits the -bugs
Andrew Dunstan [EMAIL PROTECTED] writes:
What we are talking about here is bug triage.
Really? We have a problem with too many bug reports and need a tool to help
triage them? That's the first I've heard of that.
Think about what tasks you do now and what tool would make it easier. Don't
try
Gregory Stark wrote:
The Debian system would be basically zero operational change.
pgsql-bugs would continue to exist exactly as it does now except it
would go through debbugs.
Debbugs is fine and all, but they don't seem to publish their code on a
regular basis.
--
Peter Eisentraut
Andrew Dunstan wrote:
What we are talking about here is bug triage.
I think we are actually talking about bug *tracking*.
One sensible way to do this would be to have a group of suitably
qualified volunteers who could perform this function on a roster
basis, for, say, a week or a two at a
Martijn van Oosterhout wrote:
If you want the latter, the approach would be to keep pgsql-bugs and
when a real issue comes up, bounce it to the bug tracker. Any
subsequent email discussion should then get logged in the bug report.
That's what I want. I don't want the bug tracking system to be
On Fri, 11 Aug 2006, Alvaro Herrera wrote:
I am suggesting that. I have heard all the old discussions about not
using a bugtracker, but in all fairness, I think some of us have to
create critical mass and get something started.
I will install anything, and everything, if you can get some
Marc G. Fournier wrote:
On Fri, 11 Aug 2006, Alvaro Herrera wrote:
I am suggesting that. I have heard all the old discussions about not
using a bugtracker, but in all fairness, I think some of us have to
create critical mass and get something started.
I will install anything, and
RT is easy to setup/configure/use and works well with PostgreSQL
as the backend. CPAN uses it for their bug tracker. Was there a
list of features and requirements?
Ken
On Tue, Aug 15, 2006 at 10:59:52AM -0300, Marc G. Fournier wrote:
On Fri, 11 Aug 2006, Alvaro Herrera wrote:
I am suggesting
On Tue, Aug 15, 2006 at 10:53:28AM -0500, Kenneth Marshall wrote:
RT is easy to setup/configure/use and works well with PostgreSQL
as the backend. CPAN uses it for their bug tracker. Was there a
list of features and requirements?
I don't know if we ever came up with one, but I know that the
On Tue, 15 Aug 2006, Jim C. Nasby wrote:
On Tue, Aug 15, 2006 at 10:53:28AM -0500, Kenneth Marshall wrote:
RT is easy to setup/configure/use and works well with PostgreSQL
as the backend. CPAN uses it for their bug tracker. Was there a
list of features and requirements?
I don't know if we
Jim C. Nasby wrote:
On Tue, Aug 15, 2006 at 10:53:28AM -0500, Kenneth Marshall wrote:
RT is easy to setup/configure/use and works well with PostgreSQL
as the backend. CPAN uses it for their bug tracker. Was there a
list of features and requirements?
I don't know if we ever came up with
I've used and use RT. It is web based for admin, but all the transactions
are E-Mail based.
http://www.bestpractical.com
I can also make a test queue on my instance if someone wants to play.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683
We have three candidates already -- debbugs, RT and Gnats. The first
has the advantage that was written by hackers, for hackers, so it
doesn't have any of the insane for end users stuff which annoys so
many people around here ;-) (On the other hand it does have some web
stuff for generating
Christopher Kings-Lynne wrote:
We have three candidates already -- debbugs, RT and Gnats. The first
has the advantage that was written by hackers, for hackers, so it
doesn't have any of the insane for end users stuff which annoys so
many people around here ;-) (On the other hand it does have
Jim C. Nasby [EMAIL PROTECTED] writes:
I don't know if we ever came up with one, but I know that the big deal
killer for a bug tracker is that a lot of hackers don't want to be
forced to use a web interface instead of email. So basically, to be
accepted, a bug tracker would have to have an
On Aug 16, 2006, at 12:29 , Tom Lane wrote:
So my current take on this would be that the bug tracker
would have to have a reasonable output email capability, but I'd not
necessarily insist on being able to input to it by mail.
Setting aside the email in, how would people feel about Atom or
Tom Lane wrote:
that the bug tracker would have to have a reasonable output email
capability, but I'd not necessarily insist on being able to input
to it by mail. Red Hat's present bugzilla system could be described
that way --- and while I can't say I'm in love with it, I can deal
with it.
Tom,
These days I doubt there's anyone around the project who refuses to use
a web browser at all. However, I still personally find it much more
convenient to read and respond to mailing-list postings than to have to
go and visit random web pages to find out if there's something I need to
On Fri, Aug 11, 2006 at 05:27:46PM -0400, Alvaro Herrera wrote:
Does that rails thing also have a bug tracker that integrates with
mailing lists? IIRC the show-stopper on a bug tracker was finding one
that allowed people to still use mailing lists.
AFAIU the showstopper was that people
On Friday 04 August 2006 02:20, Josh Berkus wrote:
grin Aren't I, the marketing geek, supposed to be the one whining about
this?
[snip]
* In-place upgrades (pg_upgrade)
BTW, I may get Sun to contribute an engineer for this; will get you posted.
Long time no post. This statement really
On Thu, Aug 10, 2006 at 09:02:36PM -0700, Joshua D. Drake wrote:
I think it is a combination of the two. A wiki could be used to discuss
ideas for todos, it could be used to describe TODOs in actual detail, it
could used (in conjunction with Trac) to be able to document dependecies
for
Reinoud van Leeuwen wrote:
On Thu, Aug 10, 2006 at 09:02:36PM -0700, Joshua D. Drake wrote:
I think it is a combination of the two. A wiki could be used to discuss
ideas for todos, it could be used to describe TODOs in actual detail, it
could used (in conjunction with Trac) to be able to
Neil Conway napsal(a):
However, is there a reason to use Trac beyond the fact that it is
already setup? ISTM we only need a wiki, and don't need the other
features of Trac, such as the bug tracker.
I do not agree. How you determine what release fixes the bug now? We
have web page and mailing
Joshua D. Drake wrote:
Alvaro Herrera wrote:
Jim Nasby wrote:
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
http://projects.commandprompt.com/public/pgsql/browser/tags/REL8_1_4/pgsql
What are you looking at Alvaro?
Exactly that URL, but this wasn't there when I looked. Maybe it was
being regenerated at that time?
Yeah it gets regenerated every 4 hours or so.
But I don't know why you are
I do not agree. How you determine what release fixes the bug now? We
have web page and mailing list for bug reporting but there is not any
relation between bug, patch and release(s). I think bug tracking is
necessary if we want move forward.
You can completely forget the idea of having an
Joshua D. Drake wrote:
Lastly if you review this thread you would see that Andrew and I had
already decided to wait until after Linux World to actually propose
something.
It is perhaps not surprising, but most of the discussion has been
focused on technologies (mailing lists, wikis,
Joshua D. Drake wrote:
http://projects.commandprompt.com/public/pgsql/browser/tags/REL8_1_4/pgsql
What are you looking at Alvaro?
Exactly that URL, but this wasn't there when I looked. Maybe it was
being regenerated at that time?
Yeah it gets regenerated every 4 hours or so.
Alvaro Herrera wrote:
O.k. but no one is suggesting that we use Trac as a bug tracker, or at
least I wasn't. All I was suggesting was the ability to help viewing of
specific files as listed dependencies.
I am suggesting that. I have heard all the old discussions about not
using a
Actually I'd *like* to use something better than CVSWeb, because you
know what? It sucks and I'd love to have something better. I'd also
I am not opposed to actually using taylor or something to do the
conversion instead. I just couldn't get it to work.
I think the devel version of Trac
On Fri, Aug 11, 2006 at 08:16:19AM -0700, Joshua D. Drake wrote:
I just threw the trac out there because it was already setup. I don't
care if anyone uses it or not. Nor am I suggesting that it *should* be used.
Lastly if you review this thread you would see that Andrew and I had
already
Jim C. Nasby wrote:
On Fri, Aug 11, 2006 at 08:16:19AM -0700, Joshua D. Drake wrote:
I just threw the trac out there because it was already setup. I don't
care if anyone uses it or not. Nor am I suggesting that it *should* be used.
Lastly if you review this thread you would see that
Tom Lane wrote:
Yeah, the main problem I have with TODO-on-a-wiki is the question of
quality control. I've been heard to complain that the TODO list
consists of everything Bruce thinks is a good idea, but for the most
part things don't get onto TODO without some rough consensus on the
mailing
@postgresql.org
Sent: 10/08/06 05:30
Subject: RE: [HACKERS] 8.2 features status
Two words: House Hunting ...
Yeuch. Toronto?
... will post something to -www as
soon as I have something up and running ...
Ok, cool.
/D
---(end of broadcast)---
TIP 5
Marc,
... will post something to -www as
soon as I have something up and running ...
Given that JD is already pulling something into a Trac instance, why don't we
just try using that? It has both an issue tracker and a wiki, and it's up
and running now. When we have a firmer idea what
On 8/9/06, Bruce Momjian [EMAIL PROTECTED] wrote:
Joshua D. Drake wrote:
Until you have used this, it seems strange. After you start it doesn't ;-)
Sure, but with openness comes cruft, which can be a problem too. Do we
want everyone's idea of a useful feature listed? I don't.
Why
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
On Aug 9, 2006, at 11:34 PM, Tom Lane wrote:
Mark Kirkwood [EMAIL
Jim Nasby wrote:
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
I just noticed that the code repository on
Alvaro Herrera wrote:
Jim Nasby wrote:
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
I just noticed that the
Alvaro Herrera wrote:
Jim Nasby wrote:
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
Oh and answer Jim's
On Thu, 2006-08-10 at 17:33 -0700, Joshua D. Drake wrote:
No, like the rest of the world, Trac has moved on from CVS ;)
There is CVSTrac (www.cvstrac.org), which actually predates Trac.
However, is there a reason to use Trac beyond the fact that it is
already setup? ISTM we only need a wiki,
Neil Conway wrote:
On Thu, 2006-08-10 at 17:33 -0700, Joshua D. Drake wrote:
No, like the rest of the world, Trac has moved on from CVS ;)
There is CVSTrac (www.cvstrac.org), which actually predates Trac.
However, is there a reason to use Trac beyond the fact that it is
already setup? ISTM
Merlin Moncure wrote:
On 8/9/06, Bruce Momjian [EMAIL PROTECTED] wrote:
Joshua D. Drake wrote:
Until you have used this, it seems strange. After you start it doesn't
;-)
Sure, but with openness comes cruft, which can be a problem too. Do we
want everyone's idea of a
Jim Nasby wrote:
First, +1 on Josh B.'s point about trying out Trac, since it's
already up and running. Josh D., can you just turn that on? (BTW, is
trac linked off http://commandprompt.com anywhere? I had to google to
find it yesterday...)
On Aug 9, 2006, at 11:34 PM, Tom Lane wrote:
It seems some people like the authoritative TODO list, and others want a
TODO wiki that they can add stuff to without having to get community
buy-in. I have trouble seeing how the wiki doesn't just end up being a
blog of ideas, but I see no harm in it as long as it is clear the items
haven't
Joshua D. Drake wrote:
It seems some people like the authoritative TODO list, and others want a
TODO wiki that they can add stuff to without having to get community
buy-in. I have trouble seeing how the wiki doesn't just end up being a
blog of ideas, but I see no harm in it as long as
Quoth [EMAIL PROTECTED] (Joshua D. Drake):
Josh Berkus wrote:
Bruce,
What happens now is that someone says they want to work on X, and the
community tells them that Y might be working on it, and Y gives us a
status.
What happens now is:
A starts working on X.
3 months pass
B comes to
Christopher Browne wrote:
Quoth [EMAIL PROTECTED] (Joshua D. Drake):
Josh Berkus wrote:
Bruce,
What happens now is that someone says they want to work on X, and the
community tells them that Y might be working on it, and Y gives us a
status.
What happens now is:
A starts working on X.
3
There's a LOT of unnecessary overhead in that process: having a
simple web app that lists who claimed what todo and when, any
status updates if they've voluntarily provided them, and links to
archive discussions, we could reduce the above to a 3-step process
making it vastly
Joshua D. Drake [EMAIL PROTECTED] writes:
My point was, I was going to work on some todos before feature freeze. I
asked about two specific todos. One of them was badly worded and one of
them did not represent (except in the smallest of ways) what it actually
was.
Well, it's certainly the
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
My point was, I was going to work on some todos before feature freeze. I
asked about two specific todos. One of them was badly worded and one of
them did not represent (except in the smallest of ways) what it actually
was.
What this story does do for me is reinforce the notion that it's
critical for newbie developers to work in the open, getting feedback
from the lists at an early stage about what they are doing. If you go
off in a corner and develop a patch for a TODO item, you risk having it
rejected because
Maybe the connection is that while thinking about processes, we need
to take into account the need to encourage people to get early
feedback about what they are considering doing.
We say that clearly in the developer's FAQ, but it seems it is not
enough.
I just read the developer's FAQ, and
Joshua D. Drake wrote:
Maybe the connection is that while thinking about processes, we need
to take into account the need to encourage people to get early
feedback about what they are considering doing.
We say that clearly in the developer's FAQ, but it seems it is not
enough.
I
On Wed, Aug 09, 2006 at 08:21:41AM -0700, Joshua D. Drake wrote:
From Bruce's perspective this actually doesn't add too much to the
workload. Generate the link, possibly paste some archive urls into the
wiki and then someone can come behind and clean up.
Or better yet, if editing the TODO is
We now have URLs on the TODO list to the archives, and the next FAQ item
is:
H3 id=item1.41.4) What do I do after choosing an item to
work on?/H3
PSend an email to pgsql-hackers with a proposal for what you want
to do (assuming your contribution is not trivial). Working in
so
Jim C. Nasby wrote:
On Wed, Aug 09, 2006 at 08:21:41AM -0700, Joshua D. Drake wrote:
From Bruce's perspective this actually doesn't add too much to the
workload. Generate the link, possibly paste some archive urls into the
wiki and then someone can come behind and clean up.
Or better yet, if
On Tue, Aug 08, 2006 at 10:31:00PM -0400, Bruce Momjian wrote:
bruce wrote:
bruce wrote:
OK, seems this should be a separate application, not done in the TODO
list, and I am not willing to take on that additional workload.
Let me add that anyone who has CVS commit access or wants
Bruce Momjian wrote:
I am keeping URLs in the TODO list. Why don't people submit
improvements to the TODO list, rather than adding more complexity by
making a separate wiki for every TODO item? If no one updates the TODO
item, what makes you think they are going to do somethin in a wiki?
1 - 100 of 303 matches
Mail list logo
