Peter Eisentraut wrote:
Am Dienstag, 15. April 2008 schrieb Zdenek Kotala:
JavaDB and Firebird community use Jira
Jira had already been rejected many years ago because it is not open source.
Jira is also tremendously slow. Not a good system when an individual
has to move quickly th
Peter Eisentraut napsal(a):
Am Dienstag, 15. April 2008 schrieb Zdenek Kotala:
JavaDB and Firebird community use Jira
Jira had already been rejected many years ago because it is not open source.
Yeah, I know, main point was that it is similar to bugzila.
Zdenek
--
Sent via
Am Dienstag, 15. April 2008 schrieb Zdenek Kotala:
> JavaDB and Firebird community use Jira
Jira had already been rejected many years ago because it is not open source.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgres
Peter Eisentraut napsal(a):
Bruce Momjian wrote:
That is a nice list, but are these used for bug tracking or patch
tracking?
In my experience, these two concepts become mostly the same. Just one is
classified "normal" or "critical" and the the other is tagged "wishlist"
and "patch" or "atta
Tom, All:
> Well, I can provide an easy example: my first patch [1].
A second one would be Meredith's original QBE patch. While we wouldn't have
ever included it in the core code, it would have been nice if she'd gotten a
reply explaining why.
More importantly, we *think* we haven't missed an
All,
BTW, the lead developer for ReviewBoard stopped by the PostgreSQL booth at
LUGRadio this weekend. He was interested in the possibility of us using
ReviewBoard, but not very interested in adding an e-mail interface to the
software.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
--
Sent
I'm just an observer here, but I thought I'd present an idea. Feel free to
tell me I'm nuts if you don't like it.
It seems to me that there are two main concerns in this area on discussion:
1. How to create a list of patches/review items/etc without adding a
significant amount of noise to this li
On Sat, Apr 12, 2008 at 3:46 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
> As an aside, you've reminded me about another thing that bothers me about
> Bugzilla and RT. In both cases they seem to put a lot of focus around the
> idea
> of "searching" bugs. I don't really get why.
>
Er, because
We use RT here for our trouble ticket system and the dashboard
can easily be configured to display tickets based on any search
criteria and you can have multiple views on the same screen.
The search functionality can be viewed as the tool for configuring
your views into the system, for whatever its
On Apr 11, 2008, at 12:54 PM, Tom Lane wrote:
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
In Trac, if I just want to loosely associate several tickets together
I'd use *keywords*, e.g., put "index am" in the keywords list for
several tickets, and then they'll show up prominently when I search
for
On Fri, Apr 11, 2008 at 06:46:18PM +0100, Gregory Stark wrote:
> As an aside, you've reminded me about another thing that bothers me about
> Bugzilla and RT. In both cases they seem to put a lot of focus around the
> idea of "searching" bugs. I don't really get why.
To be fair to RT, it's really
Gregory Stark wrote:
As an aside, you've reminded me about another thing that bothers me about
Bugzilla and RT. In both cases they seem to put a lot of focus around the idea
of "searching" bugs. I don't really get why.
Maybe it makes sense if you plan to be like Mozilla and have 8-year-old bug
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> In Trac, if I just want to loosely associate several tickets together
> I'd use *keywords*, e.g., put "index am" in the keywords list for
> several tickets, and then they'll show up prominently when I search
> for those terms.
Assuming you know what to
On Fri, 11 Apr 2008 18:46:18 +0100
Gregory Stark <[EMAIL PROTECTED]> wrote:
> I would think an interface which presents you with *all* unclosed
> bugs by default, perhaps organized in some way (keywords, milestones,
> etc) would be more conducive to getting attention to everything.
>
> I'm sure y
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> In Trac, if I just want to loosely associate several tickets together
> I'd use *keywords*, e.g., put "index am" in the keywords list for
> several tickets, and then they'll show up prominently when I search
> for those terms.
As an aside, you've remin
On Apr 11, 2008, at 9:30 AM, Tom Lane wrote:
Gregory Stark <[EMAIL PROTECTED]> writes:
Personally I don't think we *know* what we want to do and that's
why the wiki
is a good interim tool.
Yup, that is *exactly* the point. A wiki page is a zero-setup-cost,
flexible way of experimenting wit
Yup, that is *exactly* the point. A wiki page is a zero-setup-cost,
flexible way of experimenting with tracking commit-fest issues.
A year from now, we might have enough experience to decide that some
more-rigidly-structured tool will do what we need, but we don't have
it today. We spent enough
On Sat, Apr 12, 2008 at 3:13 AM, Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>
> > The bug trackers I've dealt with haven't got much flexibility in this
> > respect either --- the sorts of global views you can get are entirely
> > determined by the tool. I'm
Yup, that is *exactly* the point. A wiki page is a zero-setup-cost,
flexible way of experimenting with tracking commit-fest issues.
A year from now, we might have enough experience to decide that some
more-rigidly-structured tool will do what we need, but we don't have
it today. We spent enough
"Tom Lane" <[EMAIL PROTECTED]> writes:
> The bug trackers I've dealt with haven't got much flexibility in this
> respect either --- the sorts of global views you can get are entirely
> determined by the tool. I'm fairly certain that a tracker designed around
> the assumption that different entries
(I've already said that I think the wiki is a great step forward,
FWIW, and I'm not in any way suggesting that we should just drop it
and pick my favorite issue tracker or anything. However, for those
interested in discussion about theoretical benefits and cons of the
different systems...)
On Fri,
Marc G. Fournier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> In the projects I'm involved in, tends to be for used for both purposes ...
> one
> central location for everything ...
Yea, good point. I think our big question is what justification do we
have for doing things d
Tom Lane wrote:
> Gregory Stark <[EMAIL PROTECTED]> writes:
> > Personally I don't think we *know* what we want to do and that's why the
> > wiki
> > is a good interim tool.
>
> Yup, that is *exactly* the point. A wiki page is a zero-setup-cost,
> flexible way of experimenting with tracking comm
Gregory Stark <[EMAIL PROTECTED]> writes:
> Personally I don't think we *know* what we want to do and that's why the wiki
> is a good interim tool.
Yup, that is *exactly* the point. A wiki page is a zero-setup-cost,
flexible way of experimenting with tracking commit-fest issues.
A year from now,
Gregory Stark escribió:
> Personally I don't think we *know* what we want to do and that's why the wiki
> is a good interim tool. We'll see what info we need there and who needs to
> fill it in and find out what tool will fit our needs.
+1. Let's learn what we need first, and find an appropriate
On Fri, 11 Apr 2008 15:44:43 +0100
Gregory Stark <[EMAIL PROTECTED]> wrote:
> Proposing specific tools without a consensus on what that process is
> putting the cart before the horse. You pick the tools to fit what you
> want to do. We haven't decided what we want to do yet.
>
> Personally I don'
"Tom Dunstan" <[EMAIL PROTECTED]> writes:
> The reason a tracker is better imo than a wiki is that a wiki still
> needs someone to maintain an index page (or multiple index pages for
> different queues), so there's still an opportunity for something to
> fall through.
For the umpteenth time bug
On Fri, Apr 11, 2008 at 1:32 PM, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> > > The apache group seems to say the patches are indeed ignored, rather
> > > then just delayed --- for us, every patch does get a reply, however
> > > delayed.
> > >
> >
> > Bruce, I think that this comes back to
Joshua D. Drake wrote:
> On Thu, 10 Apr 2008 23:23:20 -0400 (EDT)
> Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> > Brendan Jurd wrote:
> > > I'm not saying Bruce is doing a bad job, far from it. I'm saying
> > > the job is impossible.
> > >
> > > I just wanted to correct the apparent impression
On Thu, 10 Apr 2008 23:23:20 -0400 (EDT)
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Brendan Jurd wrote:
> > I'm not saying Bruce is doing a bad job, far from it. I'm saying
> > the job is impossible.
> >
> > I just wanted to correct the apparent impression that "patches don't
> > get ignored her
On Thu, 10 Apr 2008 23:26:28 -0400
Aidan Van Dyk <[EMAIL PROTECTED]> wrote:
>
> And then anybody asking a question about the status of something gives
> you a pedestal to show how nicely your tracker works.
>
If you think that is what I am after you obviously have no idea who are
you replying t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 11, 2008 at 1:40 PM, Tom Lane wrote:
> "Brendan Jurd" writes:
>
> > Not really. I'm claiming that, to the submitter, a response that
> > hasn't happened yet and a response that is never coming look pretty
> > much identical.
>
> I und
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> Not really. I'm claiming that, to the submitter, a response that
> hasn't happened yet and a response that is never coming look pretty
> much identical.
I understand, but that seems a bit offtopic seeing that this whole
thread is about how to guarantee
On Fri, Apr 11, 2008 at 1:01 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> > I just wanted to correct the apparent impression that "patches don't
> > get ignored here". Patches get ignored. The difference between us
> > and Apache is we pretend it doesn
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > That is a nice list, but are these used for bug tracking or patch
> > tracking?
>
> In my experience, these two concepts become mostly the same. Just one is
> classified "normal" or "critical" and the the other is tagged "wishlist"
> and "patch
* Joshua D. Drake <[EMAIL PROTECTED]> [080410 23:20]:
> On Thu, 10 Apr 2008 22:47:34 -0400
> Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > If you have something to add, please do so at some time, but if you
> > > are not interested in using a tracker
Brendan Jurd wrote:
> I'm not saying Bruce is doing a bad job, far from it. I'm saying the
> job is impossible.
>
> I just wanted to correct the apparent impression that "patches don't
> get ignored here". Patches get ignored. The difference between us
> and Apache is we pretend it doesn't happ
On Thu, 10 Apr 2008 22:47:34 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > If you have something to add, please do so at some time, but if you
> > are not interested in using a tracker anyway, just don't use it and
> > ignore this thread.
>
> Hmm, we
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> I just wanted to correct the apparent impression that "patches don't
> get ignored here". Patches get ignored. The difference between us
> and Apache is we pretend it doesn't happen and don't suggest to
> submitters what action to take when it does. W
On Fri, Apr 11, 2008 at 1:06 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> I assume you also read this Apache heading:
>
> What if my patch gets ignored?
>
> Because Apache has only a small number of volunteer developers,
> and these developers are often very busy, it is p
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> If you have something to add, please do so at some time, but if you are not
> interested in using a tracker anyway, just don't use it and ignore this
> thread.
Hmm, well, I can hardly see how anyone could object to a tracker that
they didn't have to
Gregory Stark wrote:
> This thread has already consumed far too many cycles.
If you are not interested, please go away and let those of us who are
interested work out the details. So far, I've only seen you put down just
about every proposal without anything constructive coming from your side.
Gregory Stark wrote:
> The current process is about as simple for a
> submitter as it could possibly be:
Yes, but we are not talking about the process for the submitter but the
process for the developer.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to yo
Gregory Stark wrote:
> Yes, if we're just tracking patches or major proposals in a bug tracker.
> The hard part is actually deciding that they're closed.
I am of the opinion that that will be very easy in practice.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make cha
Bruce Momjian wrote:
> That is a nice list, but are these used for bug tracking or patch
> tracking?
In my experience, these two concepts become mostly the same. Just one is
classified "normal" or "critical" and the the other is tagged "wishlist"
and "patch" or "attachment" or something like th
On Thu, 10 Apr 2008 23:21:40 +0100
Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>
> > Yes Alvaro but that doesn't mean the process should be complicated
> > for the sake of being complicated.
>
> This is all utter BS though. The current process is abou
Alvaro Herrera wrote:
Gregory Stark wrote:
And indeed the closest analogue I can think of to our habit of mailing around
patches is the Linux kernel where people often do post proposed patches and
patches get signed off by a second developer. Each maintainer keeps track on
his own todo lis
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Its about efficiency. If I have to *think* about some kind of process
> that takes cycles away from other more important and interesting things
> like algorithms.
This thread has already consumed far too many cycles.
--
Gregory Stark
Enterpri
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Yes Alvaro but that doesn't mean the process should be complicated for
> the sake of being complicated.
This is all utter BS though. The current process is about as simple for a
submitter as it could possibly be:
1) If you want to send us a patch
On Thu, 10 Apr 2008 16:14:33 -0500
Decibel! <[EMAIL PROTECTED]> wrote:
> On Apr 10, 2008, at 12:52 AM, Brendan Jurd wrote:
> > The typical way to solve this is to have the tracker send an
> > automatic notification email to a list saying "Hey, there's a new
> > ticket at , come and check it out".
On Thu, 10 Apr 2008 12:13:38 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
>
> > The base requirements for this process must be so simple, so easy,
> > that even if the person has never seen a C patch in his/her life
> > they understand what is trying to be achieved.
>
On Thu, 10 Apr 2008 14:18:52 -0400
Chris Browne <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] ("Joshua D. Drake") writes:
> > The base requirements for this process must be so simple, so easy,
> > that even if the person has never seen a C patch in his/her life
> > they understand what is trying
Gregory Stark wrote:
> And indeed the closest analogue I can think of to our habit of mailing around
> patches is the Linux kernel where people often do post proposed patches and
> patches get signed off by a second developer. Each maintainer keeps track on
> his own todo list of patches to take a
"Peter Eisentraut" <[EMAIL PROTECTED]> writes:
> Marc G. Fournier wrote:
>> Do other large projects accept patches 'ad hoc' like we do? FreeBSD?
>> Linux? KDE?
>...
> Postfix is the only major project I looked at that didn't have any bug
> tracker
> linked at an obvious location.
Those are us
On Apr 10, 2008, at 12:52 AM, Brendan Jurd wrote:
The typical way to solve this is to have the tracker send an automatic
notification email to a list saying "Hey, there's a new ticket at ,
come and check it out".
And that's part of the issue... "come over to this other place to
actually look
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In the projects I'm involved in, tends to be for used for both purposes ... one
central location for everything ...
- --On Thursday, April 10, 2008 15:22:28 -0400 Bruce Momjian <[EMAIL
PROTECTED]>
wrote:
> Peter Eisentraut wrote:
>> Here is what
Peter Eisentraut wrote:
> Here is what everyone else is using:
>
> Kolab - roundup
> GnuPG - roundup
> Python - custom
FWIW Python also uses roundup.
This would be a pointless comment except that I think roundup is a bit
closer to our ways than Bugzilla.
--
Alvaro Herrera
[EMAIL PROTECTED] ("Joshua D. Drake") writes:
> The base requirements for this process must be so simple, so easy, that
> even if the person has never seen a C patch in his/her life they
> understand what is trying to be achieved.
Are you sure about that?
I think that our concern is about the so
Peter Eisentraut wrote:
> Here is what everyone else is using:
>
> FreeBSD - gnats
> Linux - bugzilla
> KDE - bugzilla
> GNOME - bugzilla
> Debian - debbugs
> Ubuntu - launchpad (proprietary)
> Mozilla - bugzilla
> OpenOffice - bugzilla
> Fedora - bugzilla
> Samba - bugzilla
> NTP - bugzilla
> Slo
Marc G. Fournier wrote:
> Do other large projects accept patches 'ad hoc' like we do? FreeBSD?
> Linux? KDE?
Here is what everyone else is using:
FreeBSD - gnats
Linux - bugzilla
KDE - bugzilla
GNOME - bugzilla
Debian - debbugs
Ubuntu - launchpad (proprietary)
Mozilla - bugzilla
OpenOffice - bu
Joshua D. Drake wrote:
> On Thu, 10 Apr 2008 11:15:08 -0400
> Aidan Van Dyk <[EMAIL PROTECTED]> wrote:
>
> > Well, only if you want to "pull" the last status (i.e. someone else,
> > not you may have updated it, and you haven't set yourself to be
> > notified on changes). But again, since it's by
* Joshua D. Drake <[EMAIL PROTECTED]> [080410 11:30]:
> On Thu, 10 Apr 2008 11:15:08 -0400
> Aidan Van Dyk <[EMAIL PROTECTED]> wrote:
>
>
> > > * Where do I comment?
> >
> > In your mail program.
>
> To where? Development discussion is supposed to happen on -hackers but
> a patch is likely on
* Joshua D. Drake <[EMAIL PROTECTED]> [080410 10:24]:
>
> Someone, anyone should be able to look exactly one place for the
> information required to process a patch.
That one place is (and I think always should be, but I'm biased) going
to be the mailling list.
>
* Joshua D. Drake <[EMAIL PROTECTED]> [080410 11:55]:
> On Thu, 10 Apr 2008 11:53:09 -0400
> Aidan Van Dyk <[EMAIL PROTECTED]> wrote:
>
> > I can grab the messageid (or mhonorc url, I've got tools to get the
> > message id out if it), directly open the message in my reader of
> > choice, and have
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > (I wonder what should happen if a message is posted to more than one
> > list.)
>
> That's a good question. I suppose there are actually multiple archive
> entries in that case --- which one is the message-id link taking me to?
The
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> (I wonder what should happen if a message is posted to more than one
> list.)
That's a good question. I suppose there are actually multiple archive
entries in that case --- which one is the message-id link taking me to?
I guess whichever list appears f
Joshua D. Drake wrote:
> The base requirements for this process must be so simple, so easy, that
> even if the person has never seen a C patch in his/her life they
> understand what is trying to be achieved.
I'm pretty sure we don't want a person who has never seen a C patch in
his life anywhere
On Thu, 10 Apr 2008 12:07:43 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > Or :)
>
> > I can open a web browser, go to tracker.postgresql.org,
> > review the list of open patches, click one, download, review,
> > comment, upload new patch if require
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> The message comes up.
>
> Granted... very, very cool that this is all linked, so +1.
>
> But now what?
Now you return, suitably enlightened, to your regularly scheduled life talking
about code (or trackers) on pgsql-hackers and other mailing lists.
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Or :)
> I can open a web browser, go to tracker.postgresql.org,
> review the list of open patches, click one, download, review, comment,
> upload new patch if required, done.
And then no one sees your revised patch (except someone watching the
track
Joshua D. Drake wrote:
> On Thu, 10 Apr 2008 11:17:37 -0400
> Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > > But now what?
> >
> > If you've got substantive comments to make, you make them by replying
> > to the original email, same as it ever was.
On Thu, 10 Apr 2008 11:53:09 -0400
Aidan Van Dyk <[EMAIL PROTECTED]> wrote:
> I can grab the messageid (or mhonorc url, I've got tools to get the
> message id out if it), directly open the message in my reader of
> choice, and have the patch, all the discussion threaded nicely, so I
My mail reade
Bruce Momjian wrote:
> Also, let me add the wiki does not have items that need
> discussion/feedback for this commit-fest. Is that going to be added
> someday?
I take that back. The March wiki has two items that are clearly not
ready to be applied but need discussion that is happening:
On Thu, 10 Apr 2008 11:41:51 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
>
> > And in looking at this further, if I look at the Column Level
> > privelages patch on the wiki, the archive page goes to a -hackers
> > email.
> >
> > http://archives.postgresql.org/pgsql-
* Joshua D. Drake <[EMAIL PROTECTED]> [080410 11:35]:
> I now need to open my mail client (fair enough, with me it is alt-tab),
> go to my projects-postgresql folder, put a search string in the search
> field, find the correct email, reply to the email with my comments, and
> possibly an updated
Bruce Momjian wrote:
> Also, let me add the wiki does not have items that need
> discussion/feedback for this commit-fest. Is that going to be added
> someday?
Sure, we can create a new section titled "items needing discussion".
--
Alvaro Herrerahttp://www.Comma
Aidan Van Dyk wrote:
> > Lastly, how is this sustainable? I don't see anything that is reducing
> > Bruce's workload. (for example)
>
> The only think that will ever reduce Bruce's workload is him trusting
> that things aren't getting overlooked. The value to the work Bruce does
> is that he real
Joshua D. Drake wrote:
> And in looking at this further, if I look at the Column Level
> privelages patch on the wiki, the archive page goes to a -hackers email.
>
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00049.php
>
> * Do I now respond to the hackers list?
Note that we expec
On Thu, 10 Apr 2008 11:17:37 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > But now what?
>
> If you've got substantive comments to make, you make them by replying
> to the original email, same as it ever was. The wiki page is an
> index of email th
On Thu, 10 Apr 2008 11:15:08 -0400
Aidan Van Dyk <[EMAIL PROTECTED]> wrote:
> > * Where do I comment?
>
> In your mail program.
To where? Development discussion is supposed to happen on -hackers but
a patch is likely on -patches. Although we are allowed to discuss on
-patches as long as it is
"Peter Eisentraut" <[EMAIL PROTECTED]> writes:
> Am Donnerstag, 10. April 2008 schrieb Tom Dunstan:
>> Even so I reckon
>> that would create vastly more noise than signal in the eventual
>> tracker - part of the existing problem has been that wading through
>> list archives is a pain for someone w
Stefan Kaltenbrunner wrote:
> Gregory Stark wrote:
> > "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> >
> >> The typical way to solve this is to have the tracker send an automatic
> >> notification email to a list saying "Hey, there's a new ticket at ,
> >> come and check it out".
> >
> > Unfortuna
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> But now what?
If you've got substantive comments to make, you make them by replying to
the original email, same as it ever was. The wiki page is an index of
email threads that need attention.
Small comments can just be left on the wiki page, but th
Brendan Jurd wrote:
> > Another is that the email list provides a
> > "push" mechanism for putting the proposed patch under the noses of a
> > bunch of people, a few of whom will hopefully take a sniff ;-).
> > A tracker is very much more of a "pull" scenario where someone has to
> > actively g
Warning - my "development" views and experiences are highly e-mail
dependant (i.e. linux-kernel style dependant). So if you don't like
email, you probably shouldn't read my response below.
* Joshua D. Drake <[EMAIL PROTECTED]> [080410 10:48]:
> I click the patch for EXPLAIN progress info:
>
>
* Bruce Momjian <[EMAIL PROTECTED]> [080410 11:06]:
> I assume you also read this Apache heading:
>
> What if my patch gets ignored?
>
> Because Apache has only a small number of volunteer developers,
> and these developers are often very busy, it is possible that your
>
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Am I supposed to look at the wiki page or bruce pages, or am I supposed
> to replying on the list about something. All of which happen during
> this fest.
We were maintaining status on both pages for this fest, as an experiment
to see which was more
Greg Smith wrote:
> Apache also pushes everything through bugzilla:
> http://httpd.apache.org/dev/patches.html
>
> The interesting quote there is:
>
> "Traditionally, patches have been submitted on the developer's mailing
> list as well as through the bug database. Unfortunately, this has made
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Donnerstag, 10. April 2008 schrieb Tom Lane:
>> Another is that the email list provides a
>> "push" mechanism for putting the proposed patch under the noses of a
>> bunch of people, a few of whom will hopefully take a sniff ;-).
>> A tracker is very
On Thu, 10 Apr 2008 07:30:32 -0700
"Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
> > I don't know what you're talking about. There are two wiki pages,
> > one for the March commitfest and one for May. How can you be
> > confused on which one are you supposed to look at?
> >
> > http://wiki.postg
On Thu, 10 Apr 2008 10:28:55 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> > I admit, I didn't use the wiki page because I got tired of trying to
> > figure out which page, or list I should be looking at. I was still
> > get js-kit replies from Bruces pages this week.
>
> I don't know what yo
Joshua D. Drake wrote:
> On Thu, 10 Apr 2008 10:15:29 -0400
> Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> > > I don't think so because it really isn't a change from what we have
> > > now. There isn't much difference from having a wiki page versus just
> > > having conversations on the patch lis
Am Donnerstag, 10. April 2008 schrieb Stefan Kaltenbrunner:
> the setup is more or less complete and the integration part was with the
> community login system (same we have now for wiki.postgresql.org) by
> adding a postgresql authentication backend as well as some experimental
> modifications to
Am Donnerstag, 10. April 2008 schrieb Tom Lane:
> Another is that the email list provides a
> "push" mechanism for putting the proposed patch under the noses of a
> bunch of people, a few of whom will hopefully take a sniff ;-).
> A tracker is very much more of a "pull" scenario where someone has t
On Thu, 10 Apr 2008 10:15:29 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> > I don't think so because it really isn't a change from what we have
> > now. There isn't much difference from having a wiki page versus just
> > having conversations on the patch list and moving email around.
>
> If
Am Donnerstag, 10. April 2008 schrieb Andrew Dunstan:
> The issue frankly is not tracker features. The issue is who is going to
> maintain it, doing pruning and triage as necessary.
I'll do it. Now just give me one I can maintain.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql
Am Donnerstag, 10. April 2008 schrieb Tom Dunstan:
> Even so I reckon
> that would create vastly more noise than signal in the eventual
> tracker - part of the existing problem has been that wading through
> list archives is a pain for someone wanting to know the current status
> of a patch. I can'
Joshua D. Drake wrote:
> On Thu, 10 Apr 2008 09:36:23 -0400
> Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> > Gregory Stark wrote:
> >
> > > Bug/request trackers are great tools, but they're just tools. They
> > > don't replace actually having to do the work. Given the really
> > > trivial number
On Thu, 10 Apr 2008 09:36:23 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Gregory Stark wrote:
>
> > Bug/request trackers are great tools, but they're just tools. They
> > don't replace actually having to do the work. Given the really
> > trivial number of patches we're dealing with really j
On Thu, 10 Apr 2008 09:29:10 -0400
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> >
>
> The issue frankly is not tracker features. The issue is who is going
> to maintain it, doing pruning and triage as necessary. No tracker
> looks after itself.
If you provide a reasonable interface to manageme
1 - 100 of 155 matches
Mail list logo
