Re: Commit Fest 2019-01 is now closed

On 2019-02-10 20:30, Magnus Hagander wrote: > On Fri, Feb 8, 2019 at 2:12 PM Peter Eisentraut > > wrote: > > On 08/02/2019 12:27, Magnus Hagander wrote: > > I'd be more than happy for somebody with morge knowledge of such > matters > > than

Re: Commit Fest 2019-01 is now closed

David Steele writes: > I'm planning to do CFM duties again this year if there are no objections... Excellent! Particularly for the last CF of a cycle, we badly need an active CFM, so it's great that you're willing to take it on. regards, tom lane

Re: Commit Fest 2019-01 is now closed

On 2/5/19 7:08 PM, Andres Freund wrote: Hi, On 2019-02-05 11:55:37 -0500, Tom Lane wrote: Bruce Momjian writes: On Mon, Feb 4, 2019 at 06:34:50AM +, Tsunakawa, Takayuki wrote: Wow, thank you so much for your hard work. The last CF for PG 12 should be tough... Agreed. I am somewhat

RE: Commit Fest 2019-01 is now closed

From: Chris Travers [mailto:chris.trav...@adjust.com] > On Fri, Feb 8, 2019 at 9:40 AM Tsunakawa, Takayuki > wrote: > I'm sorry if I repeat what someone proposed in the past, but it > would be nice if the CF app could show the number of modified lines (added > + deleted) for each patch, e.g.

Re: Commit Fest 2019-01 is now closed

On Fri, Feb 8, 2019 at 2:12 PM Peter Eisentraut < peter.eisentr...@2ndquadrant.com> wrote: > On 08/02/2019 12:27, Magnus Hagander wrote: > > I'd be more than happy for somebody with morge knowledge of such matters > > than me to think up a better color scheme. The only reason it has those > > colo

Re: Commit Fest 2019-01 is now closed

On 08/02/2019 12:27, Magnus Hagander wrote: > I'd be more than happy for somebody with morge knowledge of such matters > than me to think up a better color scheme. The only reason it has those > colors is that they're the default ones in the Bootstrap CSS framework. Can we have that column just no

Re: Commit Fest 2019-01 is now closed

On Thu, Feb 7, 2019 at 10:34 PM Gavin Flower wrote: > On 08/02/2019 00:53, Peter Eisentraut wrote: > > On 06/02/2019 21:09, Magnus Hagander wrote: > >> This has now been pushed and is available. I've set it up with stable, > >> 12 and 13 as possible versions for now, but I have not added any tags

Re: Commit Fest 2019-01 is now closed

On Fri, Feb 8, 2019 at 9:40 AM Tsunakawa, Takayuki < tsunakawa.ta...@jp.fujitsu.com> wrote: > From: Bruce Momjian [mailto:br...@momjian.us] > > I am thinking we should see which items we really want for PG 12 _now_ > > and allocate resources/help to get them done, rather than being > > surprised t

RE: Commit Fest 2019-01 is now closed

From: Bruce Momjian [mailto:br...@momjian.us] > I am thinking we should see which items we really want for PG 12 _now_ > and allocate resources/help to get them done, rather than being > surprised they didn't make it. I am glad we are in good shape with > CTEs, since that has been a long-requested

RE: Commit Fest 2019-01 is now closed

From: Gavin Flower [mailto:gavinflo...@archidevsys.co.nz] > Remember also that about 1 in 12 men are colour blind. Thank you for referring to it. I'm one of them -- I'm visually impaired and use screen reader software. I didn't notice any change in the 2019-03 CF page. I thought "Ver" is the

Re: Commit Fest 2019-01 is now closed

Andres Freund writes: > There's plenty stuff that's chugging along in development but ought to > be processed at less urgency / by different people, than the stuff > targeted to be committed soon. It's already frustrating to contribute > to postgresql for new people, but if they don't get feedbac

Re: Commit Fest 2019-01 is now closed

On Thu, Feb 7, 2019 at 4:02 AM Andres Freund wrote: > On 2019-02-07 12:53:39 +0100, Peter Eisentraut wrote: > > What is the meaning of this? If something is meant for 13, shouldn't it > > be moved to the next commit fest? > > Why? There's plenty stuff that's chugging along in development but ough

Re: Commit Fest 2019-01 is now closed

On 08/02/2019 00:53, Peter Eisentraut wrote: On 06/02/2019 21:09, Magnus Hagander wrote: This has now been pushed and is available. I've set it up with stable, 12 and 13 as possible versions for now, but I have not added any tags to the existing patches (except for one, in order to test it). Wh

Re: Commit Fest 2019-01 is now closed

Hi, On 2019-02-07 12:53:39 +0100, Peter Eisentraut wrote: > On 06/02/2019 21:09, Magnus Hagander wrote: > > This has now been pushed and is available. I've set it up with stable, > > 12 and 13 as possible versions for now, but I have not added any tags to > > the existing patches (except for one,

Re: Commit Fest 2019-01 is now closed

On 06/02/2019 21:09, Magnus Hagander wrote: > This has now been pushed and is available. I've set it up with stable, > 12 and 13 as possible versions for now, but I have not added any tags to > the existing patches (except for one, in order to test it). What is the meaning of this? If something i

Re: Commit Fest 2019-01 is now closed

On 2019-Feb-06, Magnus Hagander wrote: > This has now been pushed and is available. I've set it up with stable, 12 > and 13 as possible versions for now, but I have not added any tags to the > existing patches (except for one, in order to test it). I added a few more tags. Cool stuff, thanks! -

Re: Commit Fest 2019-01 is now closed

> On 6 Feb 2019, at 21:47, Magnus Hagander wrote: > > On Wed, Feb 6, 2019 at 9:46 PM Daniel Gustafsson > wrote: > > On 6 Feb 2019, at 21:37, Daniel Gustafsson > > wrote: > > > >> On 6 Feb 2019, at 21:09, Magnus Hagander >>

Re: Commit Fest 2019-01 is now closed

On Wed, Feb 6, 2019 at 9:46 PM Daniel Gustafsson wrote: > > On 6 Feb 2019, at 21:37, Daniel Gustafsson wrote: > > > >> On 6 Feb 2019, at 21:09, Magnus Hagander wrote: > > > >> This has now been pushed and is available. I've set it up with stable, > 12 and 13 as possible versions for now, but I

Re: Commit Fest 2019-01 is now closed

> On 6 Feb 2019, at 21:37, Daniel Gustafsson wrote: > >> On 6 Feb 2019, at 21:09, Magnus Hagander wrote: > >> This has now been pushed and is available. I've set it up with stable, 12 >> and 13 as possible versions for now, but I have not added any tags to the >> existing patches (except for

Re: Commit Fest 2019-01 is now closed

On Wed, Feb 6, 2019 at 9:38 PM Daniel Gustafsson wrote: > > On 6 Feb 2019, at 21:09, Magnus Hagander wrote: > > > This has now been pushed and is available. I've set it up with stable, > 12 and 13 as possible versions for now, but I have not added any tags to > the existing patches (except for o

Re: Commit Fest 2019-01 is now closed

> On 6 Feb 2019, at 21:09, Magnus Hagander wrote: > This has now been pushed and is available. I've set it up with stable, 12 and > 13 as possible versions for now, but I have not added any tags to the > existing patches (except for one, in order to test it). The patch has omitted the ending

Re: Commit Fest 2019-01 is now closed

On Tue, Feb 5, 2019 at 6:08 PM Andres Freund wrote: > Hi, > > On 2019-02-05 11:55:37 -0500, Tom Lane wrote: > > Bruce Momjian writes: > > > On Mon, Feb 4, 2019 at 06:34:50AM +, Tsunakawa, Takayuki wrote: > > >> Wow, thank you so much for your hard work. The last CF for PG 12 > should be to

Re: Commit Fest 2019-01 is now closed

On Tue, Feb 5, 2019 at 9:08 AM Andres Freund wrote: > What we'd talked about briefly at the Fosdem dev meeting was that a > field 'target release' or 'target branch' would be very useful to be > able to focus attention more. There's plenty stuff in the current CF > that is getting some attention,

Re: Commit Fest 2019-01 is now closed

Hi, On 2019-02-05 12:02:23 -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Tue, Feb 5, 2019 at 11:55:37AM -0500, Tom Lane wrote: > >> There's been talk periodically of having an aggressive triage effort > >> to try to sort through the pending patches and decide which ones have > >> no hope

Re: Commit Fest 2019-01 is now closed

Hi, On 2019-02-05 11:55:37 -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Mon, Feb 4, 2019 at 06:34:50AM +, Tsunakawa, Takayuki wrote: > >> Wow, thank you so much for your hard work. The last CF for PG 12 should > >> be tough... > > > Agreed. I am somewhat concerned about this and

Re: Commit Fest 2019-01 is now closed

On Tue, Feb 5, 2019 at 12:02:23PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Tue, Feb 5, 2019 at 11:55:37AM -0500, Tom Lane wrote: > >> There's been talk periodically of having an aggressive triage effort > >> to try to sort through the pending patches and decide which ones have > >>

Re: Commit Fest 2019-01 is now closed

Bruce Momjian writes: > On Tue, Feb 5, 2019 at 11:55:37AM -0500, Tom Lane wrote: >> There's been talk periodically of having an aggressive triage effort >> to try to sort through the pending patches and decide which ones have >> no hope of making it to commit in the last CF. Then, if we just pus

Re: Commit Fest 2019-01 is now closed

On Tue, Feb 5, 2019 at 11:55:37AM -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Mon, Feb 4, 2019 at 06:34:50AM +, Tsunakawa, Takayuki wrote: > >> Wow, thank you so much for your hard work. The last CF for PG 12 should > >> be tough... > > > Agreed. I am somewhat concerned about t

Re: Commit Fest 2019-01 is now closed

Bruce Momjian writes: > On Mon, Feb 4, 2019 at 06:34:50AM +, Tsunakawa, Takayuki wrote: >> Wow, thank you so much for your hard work. The last CF for PG 12 should be >> tough... > Agreed. I am somewhat concerned about this and am wondering what we can > do now to limit problems. There's

Re: Commit Fest 2019-01 is now closed

On Mon, Feb 4, 2019 at 06:34:50AM +, Tsunakawa, Takayuki wrote: > From: Michael Paquier [mailto:mich...@paquier.xyz] > > As per $subject, CF 2019-01 is now closed for business. Here is the final > > score: > > Committed: 58. > > Moved to next CF: 113. > > Withdrawn: 4. > > Rejected: 3. > > Re

RE: Commit Fest 2019-01 is now closed

From: Michael Paquier [mailto:mich...@paquier.xyz] > As per $subject, CF 2019-01 is now closed for business. Here is the final > score: > Committed: 58. > Moved to next CF: 113. > Withdrawn: 4. > Rejected: 3. > Returned with Feedback: 52. > Total: 230. Wow, thank you so much for your hard work.