On Thu, Oct 22, 2015 at 2:04 AM, Nathan Wagner wrote:
> https://granicus.if.org/pgbugs/ for anyone who hasn't and wants to take a
> look.
FYI There seems to be an encoding problem somewhere. "Đặng Minh Dũng"
is showing up as "Äặng Minh DÅ©ng" on this page:
https://granicus.if.org/pgbugs/1369
On Tue, Oct 20, 2015 at 10:39:55AM -0700, Joshua D. Drake wrote:
> So where are we at on this?
Well, I can't speak to where we are, but my system is up, running, and
seems to work well, It even attracts a few visitors.
I have been meaning to write a triage interface, but I have been stuck
doing
* Joshua D. Drake (j...@commandprompt.com) wrote:
> On 10/13/2015 11:41 AM, Bruce Momjian wrote:
>
> >FYI, I think we already have two limits for the first line summary of
> >commit messages. The limits are 64 for commit message subjects and 50
> >characters for gitweb summary pages --- anything
On 10/13/2015 11:41 AM, Bruce Momjian wrote:
FYI, I think we already have two limits for the first line summary of
commit messages. The limits are 64 for commit message subjects and 50
characters for gitweb summary pages --- anything longer is truncated.
My commit template shows me the limits
On Tue, Oct 13, 2015 at 08:39:16AM -0700, Joshua Drake wrote:
> On 10/13/2015 08:15 AM, Tom Lane wrote:
> >Andres Freund writes:
> >>On 2015-10-13 16:21:54 +0200, �lvaro Hern�ndez Tortosa wrote:
> >>>(50 chars for the commit summary, 72 chars line wrapping)
> >
> >>-1 - imo 50 chars too often make
Joshua D. Drake wrote:
> On 10/13/2015 08:15 AM, Tom Lane wrote:
> >Andres Freund writes:
> >>On 2015-10-13 16:21:54 +0200, �lvaro Hern�ndez Tortosa wrote:
> >>>(50 chars for the commit summary, 72 chars line wrapping)
> >
> >>-1 - imo 50 chars too often makes the commit summary too unspecific,
>
On 13/10/15 17:39, Joshua D. Drake wrote:
On 10/13/2015 08:15 AM, Tom Lane wrote:
Andres Freund writes:
On 2015-10-13 16:21:54 +0200, �lvaro Hern�ndez Tortosa wrote:
(50 chars for the commit summary, 72 chars line wrapping)
-1 - imo 50 chars too often makes the commit summary too unspecif
On 10/13/2015 08:15 AM, Tom Lane wrote:
Andres Freund writes:
On 2015-10-13 16:21:54 +0200, �lvaro Hern�ndez Tortosa wrote:
(50 chars for the commit summary, 72 chars line wrapping)
-1 - imo 50 chars too often makes the commit summary too unspecific,
requiring to read much more.
I agree -
Andres Freund writes:
> On 2015-10-13 16:21:54 +0200, Álvaro Hernández Tortosa wrote:
>> (50 chars for the commit summary, 72 chars line wrapping)
> -1 - imo 50 chars too often makes the commit summary too unspecific,
> requiring to read much more.
I agree --- I have a hard enough time writing a
On 13/10/15 16:24, Andres Freund wrote:
On 2015-10-13 16:21:54 +0200, Álvaro Hernández Tortosa wrote:
On 13/10/15 04:40, Tom Lane wrote:
I'm with Robert on the idea that commit log entries need to be
limited-width. I personally format them to 75 characters, so that
git_changelog's output is le
On 10/13/2015 10:21 AM, Álvaro Hernández Tortosa wrote:
On 13/10/15 04:40, Tom Lane wrote:
I'm with Robert on the idea that commit log entries need to be
limited-width. I personally format them to 75 characters, so that
git_changelog's output is less than 80 characters. regards, tom lane
On 2015-10-13 16:21:54 +0200, Álvaro Hernández Tortosa wrote:
>
> On 13/10/15 04:40, Tom Lane wrote:
> >I'm with Robert on the idea that commit log entries need to be
> >limited-width. I personally format them to 75 characters, so that
> >git_changelog's output is less than 80 characters. regards,
On 13/10/15 04:40, Tom Lane wrote:
I'm with Robert on the idea that commit log entries need to be
limited-width. I personally format them to 75 characters, so that
git_changelog's output is less than 80 characters. regards, tom lane
Little bit off-topic, but if precisely if we're trying
On Tue, Oct 13, 2015 at 4:07 PM, Andrew Dunstan wrote:
>
>
> On 10/12/2015 07:36 PM, Robert Haas wrote:
>
>> On Tue, Oct 6, 2015 at 2:33 PM, Nathan Wagner
>> wrote:
>>
>>> Two, I think any attempt to tell the developers and committers that they
>>> need to change their workflow to adapt to some
On 10/12/2015 07:36 PM, Robert Haas wrote:
On Tue, Oct 6, 2015 at 2:33 PM, Nathan Wagner wrote:
Two, I think any attempt to tell the developers and committers that they
need to change their workflow to adapt to some system is bound to fail,
so, I have asked, just what changed would you all be
Michael Paquier writes:
> On Tue, Oct 13, 2015 at 8:36 AM, Robert Haas wrote:
>> 3. Adding the metadata doesn't cause lines > 70 characters. I am not
>> a fan of the "Discussion: Message-ID-Here" format which some
>> committers have begun using, sometimes with just the message ID and
>> sometimes
On Tue, Oct 13, 2015 at 8:36 AM, Robert Haas wrote:
> 1. I'm not the only one doing it - i.e. at least 3 or 4
> moderately-frequent committers are all doing it consistently and all
> using the same format. If Tom buys into it, that's a big plus.
>
> 2. Adding the necessary metadata to a commit can
On Tue, Oct 6, 2015 at 2:33 PM, Nathan Wagner wrote:
> Two, I think any attempt to tell the developers and committers that they
> need to change their workflow to adapt to some system is bound to fail,
> so, I have asked, just what changed would you all be willing to actually
> *do*? Tom Lane is
Nathan,
If you're going further with this, one thing that we'll need is a bug
triage interface. This is something which is better done by web; that
is, a way for volunteers to go through bugs by status, and quickly
update their status and/or post follow-up questions, and then go to the
next one i
On Thu, Oct 8, 2015 at 8:11 PM, Nathan Wagner wrote:
> On Wed, Oct 07, 2015 at 03:06:50PM -0400, Stephen Frost wrote:
> > * Nathan Wagner (nw...@hydaspes.if.org) wrote:
> > > I have added full text searching to my tracker. I only index the first
> > > 50 KB of each message. There's apparently a
On Wed, Oct 07, 2015 at 03:06:50PM -0400, Stephen Frost wrote:
> * Nathan Wagner (nw...@hydaspes.if.org) wrote:
> > I have added full text searching to my tracker. I only index the first
> > 50 KB of each message. There's apparently a one MB limit on that
> > anyway, which a few messages exceed.
* Nathan Wagner (nw...@hydaspes.if.org) wrote:
> I have added full text searching to my tracker. I only index the first
> 50 KB of each message. There's apparently a one MB limit on that
> anyway, which a few messages exceed. I figure anything important is
> probably in the first 50KB. I could
On Wed, Oct 7, 2015 at 8:59 PM, Tom Lane wrote:
> Stephen Frost writes:
> > I *really* don't like the idea of rewriting the From/To completely to
> > force all mail through a relay and I'm pretty sure that "fix" would be
> > far worse than the problem.
>
> Agreed; but adding a Reply-To: header s
Stephen Frost writes:
> I *really* don't like the idea of rewriting the From/To completely to
> force all mail through a relay and I'm pretty sure that "fix" would be
> far worse than the problem.
Agreed; but adding a Reply-To: header seems quite reasonable. (Unless
gmail ignores that, which I w
On Wed, Oct 7, 2015 at 8:47 PM, Alvaro Herrera
wrote:
> Nathan Wagner wrote:
>
> > I am still working out exactly how to find multiple matching commits
> > along different branches. I'm running git patch-id on every commit,
> > but that will take a while.
>
> See src/tools/git_changelog (both th
Nathan Wagner wrote:
> I am still working out exactly how to find multiple matching commits
> along different branches. I'm running git patch-id on every commit,
> but that will take a while.
See src/tools/git_changelog (both the output and the implementation).
Isn't that rather what you want?
I have added full text searching to my tracker. I only index the first
50 KB of each message. There's apparently a one MB limit on that
anyway, which a few messages exceed. I figure anything important is
probably in the first 50KB. I could be wrong. I could re-index fairly
easily. It seems to
* Josh Berkus (j...@agliodbs.com) wrote:
> As a serious response, "reply-all" is NOT the default for common GUI
> mail clients (TB, Apple, Gmail, etc.), and I know on TB that it's not
> even possible to make it the default (I miss Kmail). So a system which
> depends on the user ... including outsi
Josh Berkus wrote:
> On 10/07/2015 11:05 AM, Alvaro Herrera wrote:
> > Josh Berkus wrote:
> >> On 10/07/2015 10:25 AM, Alvaro Herrera wrote:
> >>> Hmm, I guess we could have the bug form add
> >>> To: n...@bugs.postgresql.org
> >>> CC: pgsql-b...@postgresql.org
> >>> as headers, which should work
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> So in the pipermail interface you get the impression that after three
> messages the thread stopped. But if you go to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797804
> you realize that there's further traffic in the bug that wasn't se
Stephen Frost wrote:
> * Andres Freund (and...@anarazel.de) wrote:
> > On 2015-10-07 14:58:41 -0300, Alvaro Herrera wrote:
> > > Stephen Frost wrote:
> > > > One example of how it's used can be seen with this thread:
> > > >
> > > > http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/20
On 10/07/2015 11:05 AM, Alvaro Herrera wrote:
> Josh Berkus wrote:
>> On 10/07/2015 10:25 AM, Alvaro Herrera wrote:
>>> Hmm, I guess we could have the bug form add
>>> To: n...@bugs.postgresql.org
>>> CC: pgsql-b...@postgresql.org
>>> as headers, which should work for most people (since we reply-
* Andres Freund (and...@anarazel.de) wrote:
> On 2015-10-07 14:58:41 -0300, Alvaro Herrera wrote:
> > Stephen Frost wrote:
> > > One example of how it's used can be seen with this thread:
> > >
> > > http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2015-September/002803.html
> >
> >
On 2015-10-07 14:58:41 -0300, Alvaro Herrera wrote:
> Stephen Frost wrote:
> > One example of how it's used can be seen with this thread:
> >
> > http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/2015-September/002803.html
>
> So in the pipermail interface you get the impression that
Josh Berkus wrote:
> On 10/07/2015 10:25 AM, Alvaro Herrera wrote:
> > Hmm, I guess we could have the bug form add
> > To: n...@bugs.postgresql.org
> > CC: pgsql-b...@postgresql.org
> > as headers, which should work for most people (since we reply-all), Josh
> > Berkus being the exception.
>
> W
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> Stephen Frost wrote:
> > * Stephen Frost (sfr...@snowman.net) wrote:
> > > Perhaps it'd be better to have pgsql-bugs be the "Package owner", who
> > > also gets emails about bug activity on their packages. That way, we
> > > could have a 'jdbc'
On 10/07/2015 10:25 AM, Alvaro Herrera wrote:
> Hmm, I guess we could have the bug form add
> To: n...@bugs.postgresql.org
> CC: pgsql-b...@postgresql.org
> as headers, which should work for most people (since we reply-all), Josh
> Berkus being the exception.
Well, this will just give you more o
Stephen Frost wrote:
> * Stephen Frost (sfr...@snowman.net) wrote:
> > Perhaps it'd be better to have pgsql-bugs be the "Package owner", who
> > also gets emails about bug activity on their packages. That way, we
> > could have a 'jdbc' package whose owner is pgsql-jdbc and pgsql-bugs
> > wouldn't
* Stephen Frost (sfr...@snowman.net) wrote:
> Perhaps it'd be better to have pgsql-bugs be the "Package owner", who
> also gets emails about bug activity on their packages. That way, we
> could have a 'jdbc' package whose owner is pgsql-jdbc and pgsql-bugs
> wouldn't end up with that bug traffic (
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> Stephen Frost wrote:
> > * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > > If you want such an API, I won't stop you from using it, but I will not
> > > use it myself. Please put in message-body commands as well.
> >
> > So, unsurprisingly, debbugs
Stephen Frost wrote:
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > If you want such an API, I won't stop you from using it, but I will not
> > use it myself. Please put in message-body commands as well.
>
> So, unsurprisingly, debbugs does support all commands that can be sent
> to control@ also t
* Magnus Hagander (mag...@hagander.net) wrote:
> On Wed, Oct 7, 2015 at 4:56 PM, Stephen Frost wrote:
> > reply-all works just fine, since you like to know *exactly* how it works
> > at a technical level, I just checked and the bug email address is
> > automatically included in the Reply-To: heade
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> If you want such an API, I won't stop you from using it, but I will not
> use it myself. Please put in message-body commands as well.
So, unsurprisingly, debbugs does support all commands that can be sent
to control@ also through the n...@bugs.postgresql.o
On Wed, Oct 7, 2015 at 4:56 PM, Stephen Frost wrote:
>
> * Magnus Hagander (mag...@hagander.net) wrote:
> > On Wed, Oct 7, 2015 at 4:40 PM, Stephen Frost
> wrote:
> > > * Nathan Wagner (nw...@hydaspes.if.org) wrote:
> > > > I think I have suggested that there be a way to generate a bug id via
>
Magnus Hagander writes:
> If I understand that correct, it completely breaks the current workflow of
> "reply-all"? When I need to comment on a bug, isntead of hitting reply-all,
> i should send it to the @bugs address? Or are you saying in those cases you
> still hit reply-all but just edit the a
Magnus,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Wed, Oct 7, 2015 at 4:40 PM, Stephen Frost wrote:
> > * Nathan Wagner (nw...@hydaspes.if.org) wrote:
> > > I think I have suggested that there be a way to generate a bug id via
> > > email. Presumably someone could just copy that email
On Wed, Oct 7, 2015 at 4:40 PM, Stephen Frost wrote:
> * Nathan Wagner (nw...@hydaspes.if.org) wrote:
> > I think I have suggested that there be a way to generate a bug id via
> > email. Presumably someone could just copy that email address to make a
> > not-tracked discussion get a bug id. If
* Nathan Wagner (nw...@hydaspes.if.org) wrote:
> I think I have suggested that there be a way to generate a bug id via
> email. Presumably someone could just copy that email address to make a
> not-tracked discussion get a bug id. If the system archived all the
> lists (not hard) it would be poss
On 7 October 2015 at 02:33, Nathan Wagner wrote:
> I think even with a bug tracker the default "ignore" behavior can still
> be done. In principle, we could even mark bugs as "unconfirmed" or
> "logged" or something right away and only mark them as new or open or
> something if they actually dra
On 6 October 2015 at 21:05, Nathan Wagner wrote:
> A lot of the reports aren't bugs at all, but requests for help. My
> guess is that the users either don't know where to ask or don't
> understand the difference between a bug and not knowing how to do what
> they want to do. Perhaps a more thor
On 10/06/2015 12:03 PM, Bruce Momjian wrote:
> On Tue, Oct 6, 2015 at 03:33:20PM -0300, Alvaro Herrera wrote:
>> Joshua D. Drake wrote:
>>> On 10/06/2015 10:57 AM, Josh Berkus wrote:
On 10/06/2015 10:17 AM, Bruce Momjian wrote:
>>
Speaking of which ... this project is rich in skilled use
On Tue, Oct 6, 2015 at 03:33:20PM -0300, Alvaro Herrera wrote:
> Joshua D. Drake wrote:
> > On 10/06/2015 10:57 AM, Josh Berkus wrote:
> > >On 10/06/2015 10:17 AM, Bruce Momjian wrote:
>
> > >Speaking of which ... this project is rich in skilled users who are
> > >involved in the community but do
On 10/06/2015 11:51 AM, Alvaro Herrera wrote:
Joshua D. Drake wrote:
[I have heated water with wood till boiling point, FWIW]
Hahahah I have no doubt.
It should be, "I once heated water with wood and it didn't boil. How can I
change my process so that it will?"
Oh, I am not saying we s
Joshua D. Drake wrote:
> On 10/06/2015 11:33 AM, Alvaro Herrera wrote:
> >So I am dubious that people that currently do not contribute will
> >contribute in the future just because we change the system.
>
> No, not just because we change the software. The mindset has to change too
> and procedure
On 10/06/2015 11:33 AM, Alvaro Herrera wrote:
Joshua D. Drake wrote:
On 10/06/2015 10:57 AM, Josh Berkus wrote:
On 10/06/2015 10:17 AM, Bruce Momjian wrote:
Speaking of which ... this project is rich in skilled users who are
involved in the community but don't code. Bug triage is exactly th
On Tue, Oct 06, 2015 at 01:17:48PM -0400, Bruce Momjian wrote:
> I do think we rushed to choose a tracker a little too quickly.
Have we chosen one?
> Let me explain, from a high level, what a new tracker will change in
> our workflow.
[snip]
I won't quote your whole message, which I essentiall
Joshua D. Drake wrote:
> On 10/06/2015 10:57 AM, Josh Berkus wrote:
> >On 10/06/2015 10:17 AM, Bruce Momjian wrote:
> >Speaking of which ... this project is rich in skilled users who are
> >involved in the community but don't code. Bug triage is exactly the
> >kind of thing very part-time communi
On Tue, Oct 6, 2015 at 10:57:42AM -0700, Josh Berkus wrote:
> This is kind of like CVS. We didn't upgrade so Subversion, becuase we
> said "we already have a user-friendly interface to CVS, called Marc."
> We only moved to git when it could provide us with solid advantages.
>
> I believe the sam
On Tue, Oct 6, 2015 at 8:15 PM, Nathan Wagner wrote:
> On Tue, Oct 06, 2015 at 10:57:42AM -0700, Josh Berkus wrote:
>
> > Speaking of which ... this project is rich in skilled users who are
> > involved in the community but don't code. Bug triage is exactly the
> > kind of thing very part-time c
On 6 October 2015 at 12:32, Nathan Wagner wrote:
>
> Also, the version numbers are user reported and a bit of a mess. I
> don't think they could really be relied on as is for users trying to
> find out if a bug affects their version. Someone would have to update
> that information, and communica
On 10/06/2015 10:57 AM, Josh Berkus wrote:
On 10/06/2015 10:17 AM, Bruce Momjian wrote:
This is kind of like CVS. We didn't upgrade so Subversion, becuase we
said "we already have a user-friendly interface to CVS, called Marc."
We only moved to git when it could provide us with solid advantag
On Tue, Oct 06, 2015 at 10:57:42AM -0700, Josh Berkus wrote:
> On 10/06/2015 10:17 AM, Bruce Momjian wrote:
> > Therefore, our current default behavior is to ignore user reports,
> > unless someone takes an action to reply, record, or retain the email for
> > later review. What a tracker does is
On 10/06/2015 10:17 AM, Bruce Momjian wrote:
> First, let me say I am glad we are talking about this, and am open to
> the criticism that my and other's tracking open items by keeping them in
> our personal mailboxes is not only odd, but bizarre given the size of
> our community and the responsibil
On Tue, Oct 06, 2015 at 12:04:11PM -0500, Jaime Casanova wrote:
> I like how this page is looking now, good work.
Thank you.
> Now, AFAIU from previous mails part of the reason to have a bug
> tracker is to make easy to know when a bug was fixed. Which should be
> interpreted as: which versions
On Tue, Oct 6, 2015 at 01:05:24PM +, Nathan Wagner wrote:
> So, in order to do some clean up and see how my pgbugs page
> (https://granicus.if.org/pgbugs/) might actually work I've been going
> through bugs and marking their status. A lot of questions arise.
>
> A lot of the reports aren't b
Magnus Hagander writes:
> It doesn't actually. You can post to the bugs list without being subscribed
> and it hits moderation. If you fill out the bug form without being
> subscribed, it hits exactly the same moderation. There is no difference -
> the bug form basically just sends an email with y
On Tue, Oct 6, 2015 at 7:04 PM, Jaime Casanova <
jaime.casan...@2ndquadrant.com> wrote:
> On 6 October 2015 at 08:05, Nathan Wagner wrote:
> > A lot of the reports aren't bugs at all, but requests for help. My
> > guess is that the users either don't know where to ask or don't
> > understand the
On 6 October 2015 at 08:05, Nathan Wagner wrote:
> So, in order to do some clean up and see how my pgbugs page
> (https://granicus.if.org/pgbugs/) might actually work I've been going
> through bugs and marking their status. A lot of questions arise.
>
/* DISCLAIMER */
My opinion is not
Nathan,
* Nathan Wagner (nw...@hydaspes.if.org) wrote:
> So, in order to do some clean up and see how my pgbugs page
> (https://granicus.if.org/pgbugs/) might actually work I've been going
> through bugs and marking their status. A lot of questions arise.
Thanks for working on this!
> A lot of
So, in order to do some clean up and see how my pgbugs page
(https://granicus.if.org/pgbugs/) might actually work I've been going
through bugs and marking their status. A lot of questions arise.
A lot of the reports aren't bugs at all, but requests for help. My
guess is that the users either don
70 matches
Mail list logo
