> On Apr 12, 2018, at 9:24 AM, Ashutosh Bapat
> wrote:
>
> On Thu, Apr 12, 2018 at 6:52 PM, Alvaro Herrera
> wrote:
>>
>> Now, maybe what you suggest for open items is to create a separate view
>> using much of the commitfest app code, say
>> https://commitfest.postgresql.org/openitems/NNN
>
On Thu, Apr 12, 2018 at 6:52 PM, Alvaro Herrera wrote:
>
> Now, maybe what you suggest for open items is to create a separate view
> using much of the commitfest app code, say
> https://commitfest.postgresql.org/openitems/NNN
> I think that would probably work well.
Yes, that's what I had in mind
Ashutosh Bapat wrote:
> On Thu, Apr 12, 2018 at 6:27 PM, Alvaro Herrera
> wrote:
> > Ashutosh Bapat wrote:
> >
> >> We use commitfest app for tracking the patches submitted. It has done
> >> well. Can we re-purpose the same for tracking open items?
> >
> > I think the rules are too different to c
On Thu, Apr 12, 2018 at 6:27 PM, Alvaro Herrera wrote:
> Ashutosh Bapat wrote:
>
>> We use commitfest app for tracking the patches submitted. It has done
>> well. Can we re-purpose the same for tracking open items?
>
> I think the rules are too different to cram both in the same place.
What do yo
Ashutosh Bapat wrote:
> We use commitfest app for tracking the patches submitted. It has done
> well. Can we re-purpose the same for tracking open items?
I think the rules are too different to cram both in the same place.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL
On Thu, Apr 12, 2018 at 11:46:33AM +0530, Ashutosh Bapat wrote:
> Usually there are threads associated with the open items, then there
> are patches to solve those and owners responsible in resolving them.
> We have all the infrastructure in the commitfest app to track those
> things, may be we cou
On Wed, Apr 11, 2018 at 10:33 PM, Magnus Hagander wrote:
> On Wed, Apr 11, 2018 at 6:57 PM, Andres Freund wrote:
>>
>> On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
>> > The other proposal was that we could have a simple web app to track open
>> > items. After all, we now know what we need
On Thu, Apr 12, 2018 at 2:31 AM, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 4/11/18 10:53, Tom Lane wrote:
>>> It's not that much work to move the items rather than remove them,
>
>> Well, toward the end of the cycle, when the list of closed items is
>> quite long, then it does become a bit
> On Apr 11, 2018, at 4:58 PM, Peter Eisentraut
> wrote:
>
> On 4/11/18 10:53, Tom Lane wrote:
>> It's not that much work to move the items rather than remove them,
>
> Well, toward the end of the cycle, when the list of closed items is
> quite long, then it does become a bit of a burden to ca
Peter Eisentraut writes:
> On 4/11/18 10:53, Tom Lane wrote:
>> It's not that much work to move the items rather than remove them,
> Well, toward the end of the cycle, when the list of closed items is
> quite long, then it does become a bit of a burden to carefully cut and
> paste the item in the
On 4/11/18 10:53, Tom Lane wrote:
> It's not that much work to move the items rather than remove them,
Well, toward the end of the cycle, when the list of closed items is
quite long, then it does become a bit of a burden to carefully cut and
paste the item in the little browser window without maki
On 04/11/2018 10:06 AM, Alvaro Herrera wrote:
Andres Freund wrote:
On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
The other proposal was that we could have a simple web app to track open
items. After all, we now know what we need from it. A wiki page seems
more laborious. (The commitfes
Magnus Hagander wrote:
> (And of course, if we want to go in *any* direction away from the wiki,
> it's not going to happen in time for *this* release..)
Absolutely. But if we never start, it'll never get done.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Developmen
Andres Freund wrote:
> On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
> > The other proposal was that we could have a simple web app to track open
> > items. After all, we now know what we need from it. A wiki page seems
> > more laborious. (The commitfest app also sprung from a wiki page.)
On Wed, Apr 11, 2018 at 6:57 PM, Andres Freund wrote:
> On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
> > The other proposal was that we could have a simple web app to track open
> > items. After all, we now know what we need from it. A wiki page seems
> > more laborious. (The commitfest
On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
> The other proposal was that we could have a simple web app to track open
> items. After all, we now know what we need from it. A wiki page seems
> more laborious. (The commitfest app also sprung from a wiki page.)
Growing a number of non-iss
Jonathan S. Katz wrote:
> During some RMT discussions I had proposed formatting the open items
> into a table on the Wiki page with some useful info to help track the status
> and surface the necessary info to track down the open item.
The other proposal was that we could have a simple web app to
> On Apr 11, 2018, at 11:54 AM, Tom Lane wrote:
>
> Robert Haas writes:
>> On Wed, Apr 11, 2018 at 10:53 AM, Tom Lane wrote:
>>> What *does* take time is adding a link to the commit, so I'd happily
>>> drop that step. As Peter says, you can usually look in the commit
>>> log if you care.
>
>
Robert Haas writes:
> On Wed, Apr 11, 2018 at 10:53 AM, Tom Lane wrote:
>> What *does* take time is adding a link to the commit, so I'd happily
>> drop that step. As Peter says, you can usually look in the commit
>> log if you care.
> The trouble is that sometimes it's not very obvious which co
On Wed, Apr 11, 2018 at 10:53 AM, Tom Lane wrote:
> Ashutosh Bapat writes:
>> On Wed, Apr 11, 2018 at 6:53 PM, Peter Eisentraut
>> wrote:
>>> Do people find it useful to move the resolved items to a separate
>>> section on the page, instead of just removing them? I'm not sure that
>>> the resol
Ashutosh Bapat writes:
> On Wed, Apr 11, 2018 at 6:53 PM, Peter Eisentraut
> wrote:
>> Do people find it useful to move the resolved items to a separate
>> section on the page, instead of just removing them? I'm not sure that
>> the resolved sections are useful, compared to just using the git lo
On Wed, Apr 11, 2018 at 6:53 PM, Peter Eisentraut
wrote:
> On 2/18/18 22:42, Michael Paquier wrote:
>> Okay, I have created a skeleton of page here:
>> https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items
>> Feel free to add any bugs or issues related to v11 that need to be
>> tracked before
On 2/18/18 22:42, Michael Paquier wrote:
> Okay, I have created a skeleton of page here:
> https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items
> Feel free to add any bugs or issues related to v11 that need to be
> tracked before the release.
Do people find it useful to move the resolved item
On Fri, Feb 09, 2018 at 11:37:52AM +0530, Ashutosh Bapat wrote:
> On Fri, Feb 9, 2018 at 9:14 AM, Michael Paquier wrote:
>> Are there any objections in creating a wiki page to track all those bugs
>> and issues? We don't want to lose track of all that.
>
> +1.
Okay, I have created a skeleton of
On Fri, Feb 9, 2018 at 9:14 AM, Michael Paquier wrote:
> Hi all,
>
> I begin seeing bugs related to new features of v11 popping up around,
> like this one for procedures:
> https://www.postgresql.org/message-id/CAFj8pRDxOwPPzpA8i%2BAQeDQFj7bhVw-dR2%3D%3DrfWZ3zMGkm568Q%40mail.gmail.com
>
> Are ther
Hi all,
I begin seeing bugs related to new features of v11 popping up around,
like this one for procedures:
https://www.postgresql.org/message-id/CAFj8pRDxOwPPzpA8i%2BAQeDQFj7bhVw-dR2%3D%3DrfWZ3zMGkm568Q%40mail.gmail.com
Are there any objections in creating a wiki page to track all those bugs
and
26 matches
Mail list logo
