public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: w^3 <[email protected]>
Cc: Josh Berkus <[email protected]>
Subject: Re: 9.2beta web issues
Date: Thu, 05 Jul 2012 17:52:07 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEybVA7dEeBUekoinBpLn40jWjhYHdhzPJj=f-p1ZYPRgg@mail.gmail.com>
References: <[email protected]>
	<CABUevExe8VMTuDrX=WKoQA9T9dztvgjGtikBMCeqdupRb01=QQ@mail.gmail.com>
	<[email protected]>
	<CABUevEybVA7dEeBUekoinBpLn40jWjhYHdhzPJj=f-p1ZYPRgg@mail.gmail.com>


Excerpts from Magnus Hagander's message of jue jul 05 17:44:10 -0400 2012:
> On Thu, Jul 5, 2012 at 11:41 PM, Tom Lane <[email protected]> wrote:
> > Magnus Hagander <[email protected]> writes:
> >> IIRC we don't normally add this, because we don't want to "assign
> >> bugs" to things in beta. Also IIRC, didn't Berkus set up a whole
> >> separate list that people are supposed to report beta bugs on?
> >
> > Geez, I sure hope not, because if there is one I am not subscribed to it
> > (AFAIK), and I bet few other hackers are either.  In any case, it's the
> > height of folly to imagine that people won't try to use the bug report
> > form for beta bugs.
> 
> In that case, I definitely suggest we retire it. It's listed on both
> http://www.postgresql.org/community/lists/ and in the archives, and is
> labeled as the one where to post such reports... I think the idea was
> that Josh was going to somehow "filter" the reports before putting
> them on -bugs, making sure they were proper, etc. And that the list
> would also take *positive* test results, which we definitely don't
> want listed as bugs. But I'm definitely +1 for getting rid of the
> distinction.

That list's traffic seems a bit on the low side -- surely we've had
people testing more recently than September 2011.

-- 
Álvaro Herrera <[email protected]>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

view thread (29+ 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: 9.2beta web issues
  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