On Wed, Nov 1, 2017 at 9:04 AM, Michael Paquier
wrote:
> Anybody willing to take the hat of the commit fest manager? If nobody,
> I am fine to take the hat as default choice this time.
And now it is open. Let's the fest begin.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@p
Hi all,
At the moment of writing this email, it is 9PM AoE (Anywhere on Earth)
31st of October. This means that the next commit fest will begin in 3
hours, and that any hackers willing to register patches for this
commit fest have roughly three hours to do so (plus/minus N hours).
This current sc
On Mon, Feb 13, 2017 at 4:25 AM, Jim Nasby wrote:
> On 2/1/17 10:39 PM, Michael Paquier wrote:
>
>> On Thu, Feb 2, 2017 at 1:23 PM, Amit Kapila
>> wrote:
>>
>>> Many thanks to you for running the show. I think it might be okay if
>>> one consolidated mail is sent for all the patches that are ma
On 2/1/17 10:39 PM, Michael Paquier wrote:
On Thu, Feb 2, 2017 at 1:23 PM, Amit Kapila wrote:
Many thanks to you for running the show. I think it might be okay if
one consolidated mail is sent for all the patches that are marked
"Returned with Feedback" or "Rejected" or "Moved to next CF". OT
On Thu, Feb 2, 2017 at 1:23 PM, Amit Kapila wrote:
> Many thanks to you for running the show. I think it might be okay if
> one consolidated mail is sent for all the patches that are marked
> "Returned with Feedback" or "Rejected" or "Moved to next CF". OTOH,
> there is some value in sending a s
On Thu, Feb 2, 2017 at 8:50 AM, Michael Paquier
wrote:
> On Tue, Jan 31, 2017 at 4:01 PM, Michael Paquier
> wrote:
>> The CF finishing soon, I have done a first pass on the patches
>> remaining on it, moving patches to the next CF or updating them. There
>> are still 48 patches still on the track
On Tue, Jan 31, 2017 at 4:01 PM, Michael Paquier
wrote:
> The CF finishing soon, I have done a first pass on the patches
> remaining on it, moving patches to the next CF or updating them. There
> are still 48 patches still on the tracker when writing this email:
> Needs review: 32.
> Ready for Com
On Mon, Jan 23, 2017 at 1:17 PM, Michael Paquier
wrote:
> As of the current score of the CF, for a total of 155 patches, 52 have
> been committed, 3 rejected and 7 marked as returned with feedback. It
> may look low, but actually it is not that bad by experience looking at
> those numbers.
The CF
Michael, all,
* Michael Paquier (michael.paqu...@gmail.com) wrote:
> There is one week left for this commit fest, and now is the time to
> push for things that have a chance to get in. As of now, there is a
> total of 25 patches waiting for some love from a committer.
Many thanks for your work as
From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Michael Paquier
> - Cascading standby cannot catch up and get stuck emitting the same message
> repeatedly, a 9.3-only bug fix.
Thank you for your hard work as a CFM. For a trivial note, this is fo
On Wed, Jan 4, 2017 at 4:02 PM, Michael Paquier
wrote:
> Here are now the current stats of the patches:
> - Needs review: 82.
> - Waiting on Author: 18.
> - Ready for Committer: 18.
> Meaning that some effort is required from committers and reviewers to
> get into a better balance. For the authors
On Tue, Jan 3, 2017 at 8:41 PM, Michael Paquier
wrote:
> On Mon, Jan 2, 2017 at 2:15 AM, Fabrízio de Royes Mello
> wrote:
>> I changed the status to "In Progress".
>
> Thanks for covering my absence.
To all hackers,
Commit fest 2017-01 has now officially begun. Wi
On Mon, Jan 2, 2017 at 2:15 AM, Fabrízio de Royes Mello
wrote:
> I changed the status to "In Progress".
Thanks for covering my absence.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgs
Em sáb, 31 de dez de 2016 às 21:52, Michael Paquier <
michael.paqu...@gmail.com> escreveu:
> On Tue, Dec 27, 2016 at 12:41 PM, Michael Paquier
>
> wrote:
>
> > There are still a couple of days to register patches! So if you don't
>
> > want your fancy feature to be forgotten, please add it in tim
On Tue, Dec 27, 2016 at 12:41 PM, Michael Paquier
wrote:
> There are still a couple of days to register patches! So if you don't
> want your fancy feature to be forgotten, please add it in time to the
> CF app. Speaking of which, I am going to have a low bandwidth soon as
> that's a period of Nati
Hi all,
As mentioned a couple of weeks back, I am fine to work as commit fest
manager for 2017-01.
Here is the commit fest status at the moment I am writing this email:
Needs review: 68.
Waiting on Author: 17.
Ready for Committer: 18.
Committed: 27.
Rejected: 2.
Returned with Feedback: 6.
Total:
On Tue, Nov 1, 2016 at 11:19 PM, Michael Paquier
wrote:
> On Tue, Nov 1, 2016 at 4:53 PM, Michael Paquier
> wrote:
> > On Tue, Nov 1, 2016 at 12:20 PM, Thomas Munro
> > wrote:
> >> On Tue, Nov 1, 2016 at 4:15 PM, Peter Eisentraut
> >> wrote:
> >>> On 10/31/16 9:39 PM, Michael Paquier wrote:
>
On Tue, Nov 1, 2016 at 4:53 PM, Michael Paquier
wrote:
> On Tue, Nov 1, 2016 at 12:20 PM, Thomas Munro
> wrote:
>> On Tue, Nov 1, 2016 at 4:15 PM, Peter Eisentraut
>> wrote:
>>> On 10/31/16 9:39 PM, Michael Paquier wrote:
We are on the 1st, at least in my timezone. So the CF should start
>>
On Tue, Nov 1, 2016 at 12:20 PM, Thomas Munro
wrote:
> On Tue, Nov 1, 2016 at 4:15 PM, Peter Eisentraut
> wrote:
>> On 10/31/16 9:39 PM, Michael Paquier wrote:
>>> We are on the 1st, at least in my timezone. So the CF should start
>>> really soon, meaning that no new patches would get in. In a co
On Tue, Nov 1, 2016 at 4:15 PM, Peter Eisentraut
wrote:
> On 10/31/16 9:39 PM, Michael Paquier wrote:
>> We are on the 1st, at least in my timezone. So the CF should start
>> really soon, meaning that no new patches would get in. In a couple of
>> hours that would be fine? I recall that the last t
On 10/31/16 9:39 PM, Michael Paquier wrote:
> We are on the 1st, at least in my timezone. So the CF should start
> really soon, meaning that no new patches would get in. In a couple of
> hours that would be fine? I recall that the last times we tried to
> sync with the US East coast time.
https://
On Tue, Nov 1, 2016 at 10:27 AM, Haribabu Kommi
wrote:
> On Mon, Oct 31, 2016 at 4:31 PM, Michael Paquier
> wrote:
>>
>> On Mon, Oct 31, 2016 at 1:49 PM, Peter Eisentraut
>> wrote:
>> > Commit fest CF 2016-11 is supposed to start in about a day. I don't
>> > think a commit fest manager was chos
On Mon, Oct 31, 2016 at 4:31 PM, Michael Paquier
wrote:
> On Mon, Oct 31, 2016 at 1:49 PM, Peter Eisentraut
> wrote:
> > Commit fest CF 2016-11 is supposed to start in about a day. I don't
> > think a commit fest manager was chosen yet. Volunteers?
>
> I'd like to pass my turn on this one as C
On Mon, Oct 31, 2016 at 1:49 PM, Peter Eisentraut
wrote:
> Commit fest CF 2016-11 is supposed to start in about a day. I don't
> think a commit fest manager was chosen yet. Volunteers?
I'd like to pass my turn on this one as CFM, but I can bring in some
time for the one of January.
--
Michael
Commit fest CF 2016-11 is supposed to start in about a day. I don't
think a commit fest manager was chosen yet. Volunteers?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing lis
On Mon, Oct 3, 2016 at 2:05 AM, Michael Paquier
wrote:
>
> On Mon, Oct 3, 2016 at 2:01 PM, Michael Paquier
> wrote:
> > There was something like 60~70 patches still listed as active in the
> > CF app on Friday my time, so doing the vacuum cleanup has taken some
> > time by marking patches as retu
On Mon, Oct 3, 2016 at 2:01 PM, Michael Paquier
wrote:
> There was something like 60~70 patches still listed as active in the
> CF app on Friday my time, so doing the vacuum cleanup has taken some
> time by marking patches as returned with feedback, rejected (few) and
> moved to next CF. A couple
Hi all,
Per $subject, I would like to thank on behalf of Fabrizio everybody
who has taken the time to send patches, review them and argue about
them. This has been by experience the largest commit fest ever, with
more than 200 entries in total. The delay in stabilizing 9.6 is likely
the explanatio
On Thu, Dec 24, 2015 at 09:45:40PM +0900, Michael Paquier wrote:
> On Thu, Dec 24, 2015 at 12:09 PM, Michael Paquier
> wrote:
> > On Tue, Dec 22, 2015 at 10:45 PM, Michael Paquier
> > wrote:
> >> On Tue, Dec 22, 2015 at 4:04 PM, Michael Paquier
> >> wrote:
> >>> OK, if those don't get addressed
On Fri, Dec 25, 2015 at 5:20 AM, Gavin Flower
wrote:
> On 25/12/15 01:45, Michael Paquier wrote:
> [...]
>>
>> And the CF is no closed. Here is the final score:
>> Committed: 30.
>> Moved to next CF: 42.
>> Rejected: 9.
>> Returned with Feedback: 22.
>> Total: 103.
>> Regards,
>
>
> You didn't say
On 25/12/15 01:45, Michael Paquier wrote:
[...]
And the CF is no closed. Here is the final score:
Committed: 30.
Moved to next CF: 42.
Rejected: 9.
Returned with Feedback: 22.
Total: 103.
Regards,
You didn't say how may regards...
[More seriously]
Many thanks to you, and the other Postgres de
On Thu, Dec 24, 2015 at 6:18 PM, Tom Lane wrote:
> Michael Paquier writes:
> > And the CF is no closed. Here is the final score:
> > Committed: 30.
> > Moved to next CF: 42.
> > Rejected: 9.
> > Returned with Feedback: 22.
> > Total: 103.
>
> Many thanks to Michael for doing the CF management wo
On 12/24/2015 04:18 PM, Tom Lane wrote:
Michael Paquier writes:
And the CF is no closed. Here is the final score:
Committed: 30.
Moved to next CF: 42.
Rejected: 9.
Returned with Feedback: 22.
Total: 103.
Many thanks to Michael for doing the CF management work this time!
+1
--
Tomas Vondr
Michael Paquier writes:
> And the CF is no closed. Here is the final score:
> Committed: 30.
> Moved to next CF: 42.
> Rejected: 9.
> Returned with Feedback: 22.
> Total: 103.
Many thanks to Michael for doing the CF management work this time!
regards, tom lane
--
Sent
On Thu, Dec 24, 2015 at 12:09 PM, Michael Paquier
wrote:
> On Tue, Dec 22, 2015 at 10:45 PM, Michael Paquier
> wrote:
>> On Tue, Dec 22, 2015 at 4:04 PM, Michael Paquier
>> wrote:
>>> OK, if those don't get addressed soon, they will be moved to the next
>>> CF with the same status.
>>
>> After a
On Tue, Dec 22, 2015 at 10:45 PM, Michael Paquier
wrote:
> On Tue, Dec 22, 2015 at 4:04 PM, Michael Paquier
> wrote:
>> OK, if those don't get addressed soon, they will be moved to the next
>> CF with the same status.
>
> After a first pass, Numbers are getting down, I am just too tired to
> co
On Tue, Dec 22, 2015 at 4:04 PM, Michael Paquier
wrote:
> OK, if those don't get addressed soon, they will be moved to the next
> CF with the same status.
After a first pass, Numbers are getting down, I am just too tired to continue:
Needs review: 13.
Waiting on Author: 15.
Ready for Committer:
On Tue, Dec 22, 2015 at 3:35 PM, Tom Lane wrote:
> Michael Paquier writes:
>> To committers: there are 4 patches waiting for input.
>
> Those are:
>
> : SQL function to report log message
>
> AFAICT, there is no committer who likes this idea enough to commit it.
> It's questionable whether we nee
Michael Paquier writes:
> To committers: there are 4 patches waiting for input.
Those are:
: SQL function to report log message
AFAICT, there is no committer who likes this idea enough to commit it.
It's questionable whether we need such a feature at all, and it's even
more questionable whether
Hi all,
As of today, at the moment I am writing this message, here is the
commit fest app status:
Needs review: 20.
Waiting on Author: 24.
Ready for Committer: 4.
Committed: 29.
Moved to next CF: 11.
Rejected: 8.
Returned with Feedback: 7.
Total: 103.
This means in short that 48 out of 103 patche
On Tue, Feb 17, 2015 at 12:34 AM, Michael Paquier wrote:
> On Tue, Feb 17, 2015 at 7:39 AM, Kohei KaiGai wrote:
> > 2015-02-16 12:25 GMT+09:00 Michael Paquier :
> >>
> >>
> >> On Fri, Feb 13, 2015 at 10:06 AM, Michael Paquier
> >> wrote:
> >>>
> >>> In order to move on to the next CF, I am goin
On Wed, Feb 18, 2015 at 12:34 AM, Michael Paquier wrote:
> On Wed, Feb 18, 2015 at 5:55 AM, Corey Huinker
> wrote:
> > What is required to get the New Patch superpower? I'm also in need of it.
>
> CCing Magnus... I am not sure myself, but I would imagine that the
> commit fest needs to be "Open"
Michael Paquier wrote:
> On Wed, Feb 18, 2015 at 9:54 AM, Alvaro Herrera
> wrote:
> > Michael Paquier wrote:
> >> On Wed, Feb 18, 2015 at 5:55 AM, Corey Huinker
> >> wrote:
> >> > What is required to get the New Patch superpower? I'm also in need of it.
> >>
> >> CCing Magnus... I am not sure my
On Wed, Feb 18, 2015 at 9:54 AM, Alvaro Herrera
wrote:
> Michael Paquier wrote:
>> On Wed, Feb 18, 2015 at 5:55 AM, Corey Huinker
>> wrote:
>> > What is required to get the New Patch superpower? I'm also in need of it.
>>
>> CCing Magnus... I am not sure myself, but I would imagine that the
>> c
Michael Paquier wrote:
> On Wed, Feb 18, 2015 at 5:55 AM, Corey Huinker
> wrote:
> > What is required to get the New Patch superpower? I'm also in need of it.
>
> CCing Magnus... I am not sure myself, but I would imagine that the
> commit fest needs to be "Open" and not "In Process" to be able t
On Wed, Feb 18, 2015 at 5:55 AM, Corey Huinker wrote:
> What is required to get the New Patch superpower? I'm also in need of it.
CCing Magnus... I am not sure myself, but I would imagine that the
commit fest needs to be "Open" and not "In Process" to be able to add
patches.
--
Michael
--
Sen
What is required to get the New Patch superpower? I'm also in need of it.
On Mon, Feb 16, 2015 at 6:59 PM, Kouhei Kaigai wrote:
> > On Tue, Feb 17, 2015 at 8:50 AM, Kouhei Kaigai
> wrote:
> > >> > I couldn't find operation to add new entry on the current CF.
> > >>
> > >> Go to the bottom of th
> On Tue, Feb 17, 2015 at 8:50 AM, Kouhei Kaigai wrote:
> >> > I couldn't find operation to add new entry on the current CF.
> >>
> >> Go to the bottom of this CF:
> >> https://commitfest.postgresql.org/4/
> >> Then click on "New patch".
> >>
> > I couldn't find the "New patch" link on both of IE
On Tue, Feb 17, 2015 at 8:50 AM, Kouhei Kaigai wrote:
>> > I couldn't find operation to add new entry on the current CF.
>>
>> Go to the bottom of this CF:
>> https://commitfest.postgresql.org/4/
>> Then click on "New patch".
>>
> I couldn't find the "New patch" link on both of IE and Chrome,
> ev
ry 17, 2015 8:34 AM
> To: Kohei KaiGai
> Cc: PostgreSQL mailing lists
> Subject: Re: [HACKERS] Commit fest 2015-12 enters money time
>
> On Tue, Feb 17, 2015 at 7:39 AM, Kohei KaiGai wrote:
> > 2015-02-16 12:25 GMT+09:00 Michael Paquier :
> >>
> >>
> >> O
On Tue, Feb 17, 2015 at 7:39 AM, Kohei KaiGai wrote:
> 2015-02-16 12:25 GMT+09:00 Michael Paquier :
>>
>>
>> On Fri, Feb 13, 2015 at 10:06 AM, Michael Paquier
>> wrote:
>>>
>>> In order to move on to the next CF, I am going to go through all the
>>> remaining patches and update their status accor
2015-02-16 12:25 GMT+09:00 Michael Paquier :
>
>
> On Fri, Feb 13, 2015 at 10:06 AM, Michael Paquier
> wrote:
>>
>> In order to move on to the next CF, I am going to go through all the
>> remaining patches and update their status accordingly. And sorry for
>> slacking a bit regarding that. If you
On Fri, Feb 13, 2015 at 10:06 AM, Michael Paquier wrote:
> In order to move on to the next CF, I am going to go through all the
> remaining patches and update their status accordingly. And sorry for
> slacking a bit regarding that. If you wish to complain, of course feel
> free to post messages o
On Thu, Jan 15, 2015 at 4:05 PM, Michael Paquier
wrote:
> We are soon entering in the money time for this CF. The last month has
> been mainly a vacation period, the progress being fantomatic on many
> fronts, still there are a couple of patches that are marked as ready
> for committer:
> - Foreig
Hi all,
We are soon entering in the money time for this CF. The last month has
been mainly a vacation period, the progress being fantomatic on many
fronts, still there are a couple of patches that are marked as ready
for committer:
- Foreign table inheritance , whose first patch has been committed
Hi all,
I have been though the patches of the current CF, looking at their
related threads and updating each patch status if needed. After one
week in this CF, we have done progress on many patches, more than 2/3
of them getting some comments, reviews and/or refreshed versions.
Looking at the CF
On Mon, Dec 15, 2014 at 03:58:39PM +0200, Heikki Linnakangas wrote:
> >WITH closest_candidates AS (
> > SELECT
> > streets.gid,
> > streets.name,
> > streets.geom
> > FROM
> > nyc_streets streets
> > ORDER BY
> > streets.geom <->
> > 'SRID=26918;POINT(583571.905921312
Rodrigo Gonzalez wrote:
> I have been reading this list for a long time and I have to say that I
> thought about reviewing patches for a long timebut I am really
> scared about few things
>
> 1 - I have no knowledge at all about postgresql code so I can be doing
> things incorrectly (sayi
On 12/15/2014 02:37 AM, Michael Paquier wrote:
> Hi all,
>
> Let's begin the commit fest of December:
> https://commitfest.postgresql.org/action/commitfest_view?id=25
I have been reading this list for a long time and I have to say that I
thought about reviewing patches for a long timebut I am
On 12/15/2014 08:32 PM, Alexander Korotkov wrote:
On Mon, Dec 15, 2014 at 7:47 PM, Heikki Linnakangas
wrote:
On 12/15/2014 05:22 PM, Alexander Korotkov wrote:
On Mon, Dec 15, 2014 at 6:20 PM, Tom Lane wrote:
Alexander Korotkov writes:
On Mon, Dec 15, 2014 at 4:12 PM, Heikki Linnakangas
On Mon, Dec 15, 2014 at 7:47 PM, Heikki Linnakangas wrote:
>
> On 12/15/2014 05:22 PM, Alexander Korotkov wrote:
>
>> On Mon, Dec 15, 2014 at 6:20 PM, Tom Lane wrote:
>>
>>>
>>> Alexander Korotkov writes:
>>>
On Mon, Dec 15, 2014 at 4:12 PM, Heikki Linnakangas <
>>> hlinnakan...@vmware
On 12/15/2014 05:22 PM, Alexander Korotkov wrote:
On Mon, Dec 15, 2014 at 6:20 PM, Tom Lane wrote:
Alexander Korotkov writes:
On Mon, Dec 15, 2014 at 4:12 PM, Heikki Linnakangas <
hlinnakan...@vmware.com
wrote:
Right. I also looked at it briefly, but I wasn't sure if we really want
it. AFA
On Mon, Dec 15, 2014 at 6:20 PM, Tom Lane wrote:
>
> Alexander Korotkov writes:
> > On Mon, Dec 15, 2014 at 4:12 PM, Heikki Linnakangas <
> hlinnakan...@vmware.com
> >> wrote:
> >> Right. I also looked at it briefly, but I wasn't sure if we really want
> >> it. AFAICT, no-one has actually asked f
Alexander Korotkov writes:
> On Mon, Dec 15, 2014 at 4:12 PM, Heikki Linnakangas > wrote:
>> Right. I also looked at it briefly, but I wasn't sure if we really want
>> it. AFAICT, no-one has actually asked for that operator, it was written
>> only to be an example of an operator that would benefit
On 12/15/2014 03:45 PM, Alexander Korotkov wrote:
On Mon, Dec 15, 2014 at 4:12 PM, Heikki Linnakangas
wrote:
On 12/15/2014 08:37 AM, Michael Paquier wrote:
On Mon, Dec 15, 2014 at 3:09 PM, Tom Lane wrote:
Michael Paquier writes:
- Point to polygon distance operator
I looked at that br
On Mon, Dec 15, 2014 at 4:12 PM, Heikki Linnakangas wrote:
>
> On 12/15/2014 08:37 AM, Michael Paquier wrote:
>
>> On Mon, Dec 15, 2014 at 3:09 PM, Tom Lane wrote:
>>
>>> Michael Paquier writes:
>>>
- Point to polygon distance operator
>>> I looked at that briefly during the last fest,
On 12/15/2014 08:37 AM, Michael Paquier wrote:
On Mon, Dec 15, 2014 at 3:09 PM, Tom Lane wrote:
Michael Paquier writes:
- Point to polygon distance operator
I looked at that briefly during the last fest, but was unsure whether it
was too entangled with the GiST patches that Heikki was lookin
On Mon, Dec 15, 2014 at 3:09 PM, Tom Lane wrote:
> Michael Paquier writes:
>> - Point to polygon distance operator
> I looked at that briefly during the last fest, but was unsure whether it
> was too entangled with the GiST patches that Heikki was looking at.
Recalling my memories of this morning
Michael Paquier writes:
> Let's begin the commit fest of December:
> https://commitfest.postgresql.org/action/commitfest_view?id=25
> ...
> To committers: there are 2 patches marked as ready for committer from
> previous commit fest:
> - Foreign table inheritance
I should probably take this one.
Hi all,
Let's begin the commit fest of December:
https://commitfest.postgresql.org/action/commitfest_view?id=25
Looking at the stats at the top of the above page, there are currently
56 patches to be dealt with:
- Needs Review: 48
- Waiting on Author: 5
- Ready for Committer: 3
In short we are in
I have closed the current commit fest.
This doesn't have to mean much yet, except that it's probably time to
stop reviewing and discussing, and instead focus on committing and
polishing what is already committed.
In this commit fest, we have committed 53 out of 112 patches, so that
wasn't so bad.
On Mon, Mar 3, 2014 at 4:34 PM, Tomas Vondra wrote:
> On 1.3.2014 18:01, Peter Eisentraut wrote:
> > Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
> > Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected:
> > 4. Total: 114.
> >
> > We're still on track to achieve
On 1.3.2014 18:01, Peter Eisentraut wrote:
> Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
> Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected:
> 4. Total: 114.
>
> We're still on track to achieve about 50% committed patches, which
> would be similar to the pre
On Sun, Mar 2, 2014 at 12:56 AM, Michael Paquier
wrote:
>
> On Sun, Mar 2, 2014 at 7:43 AM, Vik Fearing
wrote:
> > On 03/01/2014 07:50 PM, Josh Berkus wrote:
> >> On 03/01/2014 09:01 AM, Peter Eisentraut wrote:
> >>> Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
> >>> Committe
On Sun, Mar 2, 2014 at 7:43 AM, Vik Fearing wrote:
> On 03/01/2014 07:50 PM, Josh Berkus wrote:
>> On 03/01/2014 09:01 AM, Peter Eisentraut wrote:
>>> Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
>>> Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected: 4.
>>> Tot
On 03/01/2014 07:50 PM, Josh Berkus wrote:
> On 03/01/2014 09:01 AM, Peter Eisentraut wrote:
>> Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
>> Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected: 4.
>> Total: 114.
>>
>> We're still on track to achieve about 50% c
On 03/01/2014 09:01 AM, Peter Eisentraut wrote:
> Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
> Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected: 4.
> Total: 114.
>
> We're still on track to achieve about 50% committed patches, which would
> be similar to the
Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
Committer: 16, Committed: 43, Returned with Feedback: 8, Rejected: 4.
Total: 114.
We're still on track to achieve about 50% committed patches, which would
be similar to the previous few commit fests. So decent job so far.
Which br
Last week:
Status Summary. Needs Review: 45, Waiting on Author: 13, Ready for
Committer: 14, Committed: 38, Returned with Feedback: 4, Rejected: 2.
Total: 116.
This week:
Status Summary. Needs Review: 43, Waiting on Author: 11, Ready for
Committer: 12, Committed: 39, Returned with Feedback: 7, R
Hi,
On 2014-02-15 08:34:19 -0500, Peter Eisentraut wrote:
> Status Summary. Needs Review: 47, Waiting on Author: 15, Ready for
> Committer: 12, Committed: 37, Returned with Feedback: 3, Rejected: 2.
> Total: 116.
>
> This week:
>
> Status Summary. Needs Review: 45, Waiting on Author: 13, Ready f
Last week:
Status Summary. Needs Review: 47, Waiting on Author: 15, Ready for
Committer: 12, Committed: 37, Returned with Feedback: 3, Rejected: 2.
Total: 116.
This week:
Status Summary. Needs Review: 45, Waiting on Author: 13, Ready for
Committer: 14, Committed: 38, Returned with Feedback: 4, R
Last week:
Status Summary. Needs Review: 49, Waiting on Author: 18, Ready for
Committer: 9, Committed: 33, Returned with Feedback: 3, Rejected: 1.
Total: 113.
This week:
Status Summary. Needs Review: 47, Waiting on Author: 15, Ready for
Committer: 12, Committed: 37, Returned with Feedback: 3, Re
Last week:
Status Summary. Needs Review: 66, Waiting on Author: 16, Ready for
Committer: 9, Committed: 20, Returned with Feedback: 2. Total: 113.
This week:
Status Summary. Needs Review: 49, Waiting on Author: 18, Ready for
Committer: 9, Committed: 33, Returned with Feedback: 3, Rejected: 1.
Tot
On 01/23/2014 08:11 AM, Peter Eisentraut wrote:
We started this commit fest with 103 patches and got off to a flyer,
with 20 patches committed during the first week. Somehow we ended up
with 113 patches at the end of the first week, but let's please leave it
at that.
I'm tracking down patch au
We started this commit fest with 103 patches and got off to a flyer,
with 20 patches committed during the first week. Somehow we ended up
with 113 patches at the end of the first week, but let's please leave it
at that.
I'm tracking down patch authors who have not signed up for a review.
I'll als
Reminder: Commit fest 2014-01, the fourth and final commit fest in
the PostgreSQL 9.4 development cycle, will start this Wednesday, January
15. If you have a patch that you would like to see considered for
inclusion into PostgreSQL 9.4, please register it in the commit fest
application:
https
On Wed, Jan 8, 2014 at 8:43 PM, Joshua D. Drake
wrote:
>
>
> On 01/08/2014 02:38 PM, Josh Berkus wrote:
>>
>>
>> On 01/08/2014 02:04 PM, Peter Eisentraut wrote:
>>>
>>> Anyone else?
>>>
>>> Or you'll have to deal with me again?
>>>
>>
>> I vote for Peter.
>>
>
> +1
>
+1
--
Fabrízio de Royes Mell
On 01/08/2014 02:38 PM, Josh Berkus wrote:
On 01/08/2014 02:04 PM, Peter Eisentraut wrote:
Anyone else?
Or you'll have to deal with me again?
I vote for Peter.
+1
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Servic
On 01/08/2014 02:04 PM, Peter Eisentraut wrote:
> Anyone else?
>
> Or you'll have to deal with me again?
>
>
I vote for Peter.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscript
Anyone else?
Or you'll have to deal with me again?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Dec 17, 2013 at 7:14 PM, Peter Eisentraut wrote:
> On 12/17/13, 10:19 AM, Tom Lane wrote:
>> Perhaps we should just move all the Needs Review and RFC patches forward
>> to the next fest, so we don't forget about them?
>
> This was done the last few times, but it has caused some controversy
On 12/17/13, 10:19 AM, Tom Lane wrote:
> Perhaps we should just move all the Needs Review and RFC patches forward
> to the next fest, so we don't forget about them?
This was done the last few times, but it has caused some controversy.
One problem was that a number of patches arrived in this commit
Peter Eisentraut writes:
> Committers should now try to get the Ready for Committer queue cleared.
I'm still hacking on the WITHIN GROUP patch, and will look at the planner
indexes thing after that's done.
> That leaves 8 patches that haven't been reviewed. If you take a look,
> you can imagine
The commit fest is closed. Final score:
Needs Review: 8, Ready for Committer: 13, Committed: 36, Returned with
Feedback: 42, Rejected: 9. Total: 108.
All patches that were in Waiting on Author or Needs Review state and
have received a decent review have been moved to Returned with Feedback
stat
Last week's status:
Fri Nov 29
Status Summary. Needs Review: 29, Waiting on Author: 33, Ready for
Committer: 13, Committed: 24, Returned with Feedback: 5, Rejected: 5.
Total: 109.
Current status:
Fri Dec 6 10:55
Status Summary. Needs Review: 24, Waiting on Author: 21, Ready for
Committer: 14,
Last week's status:
Fri Nov 22
Status Summary. Needs Review: 47, Waiting on Author: 28, Ready for
Committer: 10, Committed: 18, Returned with Feedback: 3, Rejected: 3.
Total: 109.
Current status:
Fri Nov 29
Status Summary. Needs Review: 29, Waiting on Author: 33, Ready for
Committer: 13, Commi
On 22-11-2013 11:07, Pavel Golub wrote:
> Is is possible to add small patch to the current commit fest?
>
No. Deadline was 11/15. Add it to next CF [1].
[1] https://commitfest.postgresql.org/action/commitfest_view?id=21
--
Euler Taveira Timbira - http://www.timbira.com.br
Hello, Peter.
Is is possible to add small patch to the current commit fest?
You wrote:
PE> We started with
PE> Fri Nov 15
PE> Status Summary. Needs Review: 79, Waiting on Author: 7, Ready for
PE> Committer: 5, Committed: 7, Returned with Feedback: 3, Rejected: 1. Total:
102.
PE> We are now a
We started with
Fri Nov 15
Status Summary. Needs Review: 79, Waiting on Author: 7, Ready for Committer: 5,
Committed: 7, Returned with Feedback: 3, Rejected: 1. Total: 102.
We are now at
Fri Nov 22
Status Summary. Needs Review: 47, Waiting on Author: 28, Ready for Committer:
10, Committed: 1
Reminder: Commit fest 2013-11, the third commit fest (out of four) in
the PostgreSQL development cycle, will start this Friday, November 15.
If you have a patch that you would like to see considered for inclusion
into PostgreSQL 9.4, please register it in the commit fest application
before Friday:
1 - 100 of 339 matches
Mail list logo