Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-02 Thread Kevin Grittner
On Tue, Mar 1, 2016 at 7:47 PM, Michael Paquier wrote: > 2016-09 has been created then: > https://commitfest.postgresql.org/10/ > People, feel free to park future patches there. I think that should be in status "open" rather than "future". -- Kevin Grittner EDB: http://www.enterprisedb.com The

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread Michael Paquier
On Wed, Mar 2, 2016 at 5:46 AM, Magnus Hagander wrote: > Yes, it's trivial to rename. That's the only advantage of our ugly url > scheme which uses the surrogate key in the url instead of the actual name of > the CF :) 2016-09 has been created then: https://commitfest.postgresql.org/10/ People, f

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread Magnus Hagander
On Tue, Mar 1, 2016 at 3:40 PM, Tom Lane wrote: > Magnus Hagander writes: > > On Tue, Mar 1, 2016 at 10:12 AM, Alvaro Herrera < > alvhe...@2ndquadrant.com> > > wrote: > >> Magnus Hagander wrote: > >>> Yeah, we can do that. I'd suggest we either name it based on the > current > >>> tentative date

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread Tom Lane
Magnus Hagander writes: > On Tue, Mar 1, 2016 at 10:12 AM, Alvaro Herrera > wrote: >> Magnus Hagander wrote: >>> Yeah, we can do that. I'd suggest we either name it based on the current >>> tentative date for CF1 (september), or name it specificaly "9.7-first" or >>> something like that rather th

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread David Steele
On 3/1/16 3:35 PM, Kevin Grittner wrote: > On Tue, Mar 1, 2016 at 2:28 PM, Magnus Hagander wrote: >> On Tue, Mar 1, 2016 at 10:12 AM, Alvaro Herrera >> wrote: >>> Magnus Hagander wrote: > I'd suggest we either name it based on the current tentative date for CF1 (september), or name it

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread David Steele
On 3/1/16 3:28 PM, Magnus Hagander wrote: > On Tue, Mar 1, 2016 at 10:12 AM, Alvaro Herrera > Magnus Hagander wrote: > > > Yeah, we can do that. I'd suggest we either name it based on the current > > tentative date for CF1 (september), or name it specificaly "9.7-first" > or > > so

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread Kevin Grittner
On Tue, Mar 1, 2016 at 2:28 PM, Magnus Hagander wrote: > On Tue, Mar 1, 2016 at 10:12 AM, Alvaro Herrera > wrote: >> Magnus Hagander wrote: >>> I'd suggest we either name it based on the current tentative >>> date for CF1 (september), or name it specificaly "9.7-first" or >>> something like tha

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread Magnus Hagander
On Tue, Mar 1, 2016 at 10:12 AM, Alvaro Herrera wrote: > Magnus Hagander wrote: > > On Tue, Mar 1, 2016 at 8:09 AM, Michael Paquier < > michael.paqu...@gmail.com> > > wrote: > > > > > Hi all, > > > > > > I guess that commit fest 2016-03 is going to begin soon, at which > > > point nobody will be

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread Alvaro Herrera
Magnus Hagander wrote: > On Tue, Mar 1, 2016 at 8:09 AM, Michael Paquier > wrote: > > > Hi all, > > > > I guess that commit fest 2016-03 is going to begin soon, at which > > point nobody will be able to add new patches because > > 1) already closed CF don't accept them. > > 2) A CF currently runn

Re: [HACKERS] Addition of extra commit fest entry to park future patches

2016-03-01 Thread Magnus Hagander
On Tue, Mar 1, 2016 at 8:09 AM, Michael Paquier wrote: > Hi all, > > I guess that commit fest 2016-03 is going to begin soon, at which > point nobody will be able to add new patches because > 1) already closed CF don't accept them. > 2) A CF currently running neither. > I propose to create an ext