Re: Commitfest Manager for March
> On 1 Apr 2024, at 09:05, Andrey M. Borodin wrote: > > As of April 1 there are 97 committed patches. Hello everyone! March Commitfest is closed. ~40 CF entries were committed since April 1st. Despite some drawbacks discussed in nearby threads, its still huge amount of work and significant progress for the project. Thanks to everyone involved! The number is approximate, because in some cases I could not clearly determine status. I pinged authors to do so. 26 entries are RWF\Rejected\Withdrawn. Michael noted that I moved to next CF some entries that wait for the author more then couple of weeks. I'm going to revise WoA items in 2024-07 and RwF some of them to reduce CF bloat. If authors are still interested in continuing work of returned items, they are free to provide an answer and to change status back to Needs Review. I've removed all "target version = 17" attribute and switched statuses of a lot of entries. I'm afraid there might be some errors. If I determined status of your patch erroneously, please accept my apologise and correct the error. Thanks! Best regards, Andrey Borodin.
Re: Commitfest Manager for March
Hi, In "Re: Commitfest Manager for March" on Mon, 1 Apr 2024 11:57:27 +0300, Heikki Linnakangas wrote: > On 01/04/2024 09:05, Andrey M. Borodin wrote: >> I think it makes sense to close this commitfest only after Feature >> Freeze on April 8, 2024 at 0:00 AoE. >> What do you think? > > +1. IIRC that's how it's been done in last commitfest in previous > years too. Thanks for extending the period. Could someone review my patches for this commitfest? 1. https://commitfest.postgresql.org/47/4681/ Make COPY format extendable: Extract COPY TO format implementations Status: Needs review 2. https://commitfest.postgresql.org/47/4791/ meson: Specify -Wformat as a common warning flag for extensions Status: Ready for Committer Thanks, -- kou
Re: Commitfest Manager for March
On 01/04/2024 09:05, Andrey M. Borodin wrote: I think it makes sense to close this commitfest only after Feature Freeze on April 8, 2024 at 0:00 AoE. What do you think? +1. IIRC that's how it's been done in last commitfest in previous years too. -- Heikki Linnakangas Neon (https://neon.tech)
Re: Commitfest Manager for March
> On 20 Mar 2024, at 18:13, wenhui qiu wrote: > > Could you take a look at the patch > (https://commitfest.postgresql.org/47/4284/),How about your opinion The patch is currently in the "Ready for Committer" state. It's up to the committer to decide which one to pick. There are 22 proposed patches and many committers are dealing with the consequences of what has already been committed (build farm failures, open issues, post-commit notifications, etc.). If I was a committer, I wouldn't commit a new join kind at the door of feature freeze. If I was the author of this patch, I'd consider attracting more reviewers and testers to increase chances of the patch in July CF. Thanks for your work! Best regards, Andrey Borodin. PS. Plz post the answer below quoted text. That’s common practice here.
Re: Commitfest Manager for March
> On 1 Mar 2024, at 17:29, Daniel Gustafsson wrote: > > It is now March 1 in all timezones, so I have switched 202403 to In Progress > and 202307 to Open. There are a total of 331 patches registered with 286 of > those in an open state, 24 of those have been around for 10 CF's or more. As of April 1 there are 97 committed patches. Incredible amount of work! Thanks to all committers, patch authors and reviewers. Still there are 205 open patches, 19 of them are there for 10+ CFs. I considered reducing this number by rejecting couple of my patches. But that author-part of my brain resisted in an offlist conversation. I think it makes sense to close this commitfest only after Feature Freeze on April 8, 2024 at 0:00 AoE. What do you think? Best regards, Andrey Borodin.
Re: Commitfest Manager for March
Hi Aleksander Alekseev Could you take a look at the patch ( https://commitfest.postgresql.org/47/4284/),How about your opinion Thanks On Tue, 12 Mar 2024 at 21:41, Aleksander Alekseev wrote: > Hi Andrey, > > > > If you need any help please let me know. > > > > Aleksander, I would greatly appreciate if you join me in managing CF. > Together we can move more stuff :) > > Currently, I'm going through "SQL Commands". And so far I had not come > to "Performance" and "Server Features" at all... So if you can handle > updating statuses of that sections - that would be great. > > OK, I'll take care of the "Performance" and "Server Features" > sections. I submitted my summaries of the entries triaged so far to > the corresponding thread [1]. > > [1]: > https://www.postgresql.org/message-id/CAJ7c6TN9SnYdq%3DkfP-txgo5AaT%2Bt9YU%2BvQHfLBZqOBiHwoipAg%40mail.gmail.com > > -- > Best regards, > Aleksander Alekseev > > >
Re: Commitfest Manager for March
Hi Andrey, > > If you need any help please let me know. > > Aleksander, I would greatly appreciate if you join me in managing CF. > Together we can move more stuff :) > Currently, I'm going through "SQL Commands". And so far I had not come to > "Performance" and "Server Features" at all... So if you can handle updating > statuses of that sections - that would be great. OK, I'll take care of the "Performance" and "Server Features" sections. I submitted my summaries of the entries triaged so far to the corresponding thread [1]. [1]: https://www.postgresql.org/message-id/CAJ7c6TN9SnYdq%3DkfP-txgo5AaT%2Bt9YU%2BvQHfLBZqOBiHwoipAg%40mail.gmail.com -- Best regards, Aleksander Alekseev
Re: Commitfest Manager for March
> On 4 Mar 2024, at 17:09, Aleksander Alekseev wrote: > > If you need any help please let me know. Aleksander, I would greatly appreciate if you join me in managing CF. Together we can move more stuff :) Currently, I'm going through "SQL Commands". And so far I had not come to "Performance" and "Server Features" at all... So if you can handle updating statuses of that sections - that would be great. Best regards, Andrey Borodin.
Re: Commitfest Manager for March
Hi, > >> The call for a CFM volunteer is still open. > > > > I always wanted to try. And most of the stuff I'm interested in is already > > committed. > > > > But given importance of last commitfest before feature freeze, we might be > > interested in more experienced CFM. > > If I can do something useful - I'm up for it. > > I'm absolutely convinced you have more than enough experience with postgres > hacking to do an excellent job. I'm happy to give a hand as well. > > Thanks for volunteering! > > (someone from pginfra will give you the required admin permissions on the CF > app) Thanks for volunteering, Andrey! If you need any help please let me know. -- Best regards, Aleksander Alekseev
Re: Commitfest Manager for March
> On 1 Mar 2024, at 14:57, Andrey M. Borodin wrote: > >> On 1 Mar 2024, at 17:29, Daniel Gustafsson wrote: >> >> The call for a CFM volunteer is still open. > > I always wanted to try. And most of the stuff I'm interested in is already > committed. > > But given importance of last commitfest before feature freeze, we might be > interested in more experienced CFM. > If I can do something useful - I'm up for it. I'm absolutely convinced you have more than enough experience with postgres hacking to do an excellent job. I'm happy to give a hand as well. Thanks for volunteering! (someone from pginfra will give you the required admin permissions on the CF app) -- Daniel Gustafsson
Re: Commitfest Manager for March
> On 1 Mar 2024, at 17:29, Daniel Gustafsson wrote: > > The call for a CFM volunteer is still open. I always wanted to try. And most of the stuff I'm interested in is already committed. But given importance of last commitfest before feature freeze, we might be interested in more experienced CFM. If I can do something useful - I'm up for it. Best regards, Andrey Borodin.
Re: Commitfest Manager for March
> On 29 Feb 2024, at 22:26, Daniel Gustafsson wrote: > We are now hours away from starting the last commitfest for v17 It is now March 1 in all timezones, so I have switched 202403 to In Progress and 202307 to Open. There are a total of 331 patches registered with 286 of those in an open state, 24 of those have been around for 10 CF's or more. The call for a CFM volunteer is still open. -- Daniel Gustafsson
Commitfest Manager for March
We are now hours away from starting the last commitfest for v17 and AFAICS there have been no volunteers for the position of Commitfest manager (cfm) yet. As per usual it's likely beneficial if the CFM of the last CF before freeze is someone with an seasoned eye to what can make it and what can't, but the important part is that we get someone with the time and energy to invest. Anyone interested? -- Daniel Gustafsson
Re: Commitfest manager January 2024
On Fri, 19 Jan 2024 at 09:19, Peter Smith wrote: > > Hi Vignesh, > > If you would like any assistance processing the 100s of CF entries I > am happy to help in some way. Thanks Peter, that will be great. Regards, Vignesh
Re: Commitfest manager January 2024
Hi Vignesh, If you would like any assistance processing the 100s of CF entries I am happy to help in some way. == Kind Regards,, Peter Smith. Fujitsu Australia
Re: Commitfest manager January 2024
On Tue, 2 Jan 2024 at 15:43, Magnus Hagander wrote: > > On Tue, Jan 2, 2024 at 3:45 AM vignesh C wrote: > > > > On Mon, 1 Jan 2024 at 21:01, Magnus Hagander wrote: > > > > > > On Mon, Jan 1, 2024 at 4:35 AM vignesh C wrote: > > > > > > > > On Sun, 24 Dec 2023 at 18:40, vignesh C wrote: > > > > > > > > > > On Sun, 24 Dec 2023 at 07:16, Michael Paquier > > > > > wrote: > > > > > > > > > > > > On Sat, Dec 23, 2023 at 08:52:38AM +0530, vignesh C wrote: > > > > > > > I didn't see anyone volunteering for the January Commitfest, so > > > > > > > I'll > > > > > > > volunteer to be CF manager for January 2024 Commitfest. > > > > > > > > > > > > (Adding Magnus in CC.) > > > > > > > > > > > > That would be really helpful. Thanks for helping! Do you have the > > > > > > admin rights on the CF app? You are going to require them in order > > > > > > to > > > > > > mark the CF as in-process, and you would also need to switch the CF > > > > > > after that from "Future" to "Open" so as people can still post > > > > > > patches once January one begins. > > > > > > > > > > I don't have admin rights for the CF app. Please provide admin rights. > > > > > > > > I have not yet got the admin rights, Kindly provide admin rights for > > > > the CF app. > > > > > > It's been christmas holidays... > > > > > > > > > What's your community username? > > > > My username is vignesh.postgres > > CF admin permissions granted! Thanks, I have updated the commitfest 2024-01 to In Progress and commitfest 2024-03 to Open. Regards, Vignesh
Re: Commitfest manager January 2024
On Tue, Jan 2, 2024 at 3:45 AM vignesh C wrote: > > On Mon, 1 Jan 2024 at 21:01, Magnus Hagander wrote: > > > > On Mon, Jan 1, 2024 at 4:35 AM vignesh C wrote: > > > > > > On Sun, 24 Dec 2023 at 18:40, vignesh C wrote: > > > > > > > > On Sun, 24 Dec 2023 at 07:16, Michael Paquier > > > > wrote: > > > > > > > > > > On Sat, Dec 23, 2023 at 08:52:38AM +0530, vignesh C wrote: > > > > > > I didn't see anyone volunteering for the January Commitfest, so I'll > > > > > > volunteer to be CF manager for January 2024 Commitfest. > > > > > > > > > > (Adding Magnus in CC.) > > > > > > > > > > That would be really helpful. Thanks for helping! Do you have the > > > > > admin rights on the CF app? You are going to require them in order to > > > > > mark the CF as in-process, and you would also need to switch the CF > > > > > after that from "Future" to "Open" so as people can still post > > > > > patches once January one begins. > > > > > > > > I don't have admin rights for the CF app. Please provide admin rights. > > > > > > I have not yet got the admin rights, Kindly provide admin rights for the > > > CF app. > > > > It's been christmas holidays... > > > > > > What's your community username? > > My username is vignesh.postgres CF admin permissions granted! //Magnus
Re: Commitfest manager January 2024
On Mon, 1 Jan 2024 at 21:01, Magnus Hagander wrote: > > On Mon, Jan 1, 2024 at 4:35 AM vignesh C wrote: > > > > On Sun, 24 Dec 2023 at 18:40, vignesh C wrote: > > > > > > On Sun, 24 Dec 2023 at 07:16, Michael Paquier wrote: > > > > > > > > On Sat, Dec 23, 2023 at 08:52:38AM +0530, vignesh C wrote: > > > > > I didn't see anyone volunteering for the January Commitfest, so I'll > > > > > volunteer to be CF manager for January 2024 Commitfest. > > > > > > > > (Adding Magnus in CC.) > > > > > > > > That would be really helpful. Thanks for helping! Do you have the > > > > admin rights on the CF app? You are going to require them in order to > > > > mark the CF as in-process, and you would also need to switch the CF > > > > after that from "Future" to "Open" so as people can still post > > > > patches once January one begins. > > > > > > I don't have admin rights for the CF app. Please provide admin rights. > > > > I have not yet got the admin rights, Kindly provide admin rights for the CF > > app. > > It's been christmas holidays... > > > What's your community username? My username is vignesh.postgres Regards, Vignesh
Re: Commitfest manager January 2024
On Mon, Jan 1, 2024 at 4:35 AM vignesh C wrote: > > On Sun, 24 Dec 2023 at 18:40, vignesh C wrote: > > > > On Sun, 24 Dec 2023 at 07:16, Michael Paquier wrote: > > > > > > On Sat, Dec 23, 2023 at 08:52:38AM +0530, vignesh C wrote: > > > > I didn't see anyone volunteering for the January Commitfest, so I'll > > > > volunteer to be CF manager for January 2024 Commitfest. > > > > > > (Adding Magnus in CC.) > > > > > > That would be really helpful. Thanks for helping! Do you have the > > > admin rights on the CF app? You are going to require them in order to > > > mark the CF as in-process, and you would also need to switch the CF > > > after that from "Future" to "Open" so as people can still post > > > patches once January one begins. > > > > I don't have admin rights for the CF app. Please provide admin rights. > > I have not yet got the admin rights, Kindly provide admin rights for the CF > app. It's been christmas holidays... What's your community username? //Magnus
Re: Commitfest manager January 2024
On Sat, Dec 23, 2023 at 8:53 AM vignesh C wrote: > > Hi, > > I didn't see anyone volunteering for the January Commitfest, so I'll > volunteer to be CF manager for January 2024 Commitfest. I can assist with the January 2024 Commitfest. Thanks and Regards, Shubham Khanna.
Re: Commitfest manager January 2024
On Sun, 24 Dec 2023 at 18:40, vignesh C wrote: > > On Sun, 24 Dec 2023 at 07:16, Michael Paquier wrote: > > > > On Sat, Dec 23, 2023 at 08:52:38AM +0530, vignesh C wrote: > > > I didn't see anyone volunteering for the January Commitfest, so I'll > > > volunteer to be CF manager for January 2024 Commitfest. > > > > (Adding Magnus in CC.) > > > > That would be really helpful. Thanks for helping! Do you have the > > admin rights on the CF app? You are going to require them in order to > > mark the CF as in-process, and you would also need to switch the CF > > after that from "Future" to "Open" so as people can still post > > patches once January one begins. > > I don't have admin rights for the CF app. Please provide admin rights. I have not yet got the admin rights, Kindly provide admin rights for the CF app. Regards, Vignesh
Re: Commitfest manager January 2024
On Sun, 24 Dec 2023 at 07:16, Michael Paquier wrote: > > On Sat, Dec 23, 2023 at 08:52:38AM +0530, vignesh C wrote: > > I didn't see anyone volunteering for the January Commitfest, so I'll > > volunteer to be CF manager for January 2024 Commitfest. > > (Adding Magnus in CC.) > > That would be really helpful. Thanks for helping! Do you have the > admin rights on the CF app? You are going to require them in order to > mark the CF as in-process, and you would also need to switch the CF > after that from "Future" to "Open" so as people can still post > patches once January one begins. I don't have admin rights for the CF app. Please provide admin rights. Regards, Vignesh
Re: Commitfest manager January 2024
On Sat, Dec 23, 2023 at 08:52:38AM +0530, vignesh C wrote: > I didn't see anyone volunteering for the January Commitfest, so I'll > volunteer to be CF manager for January 2024 Commitfest. (Adding Magnus in CC.) That would be really helpful. Thanks for helping! Do you have the admin rights on the CF app? You are going to require them in order to mark the CF as in-process, and you would also need to switch the CF after that from "Future" to "Open" so as people can still post patches once January one begins. -- Michael signature.asc Description: PGP signature
Commitfest manager January 2024
Hi, I didn't see anyone volunteering for the January Commitfest, so I'll volunteer to be CF manager for January 2024 Commitfest. Regards, Vignesh
Re: Commitfest manager November 2023
On Thu, Nov 2, 2023 at 4:35 PM Daniel Gustafsson wrote: > > > On 1 Nov 2023, at 07:33, John Naylor wrote: > > > > I didn't see any recent mentions in the archives, so I'll volunteer to > > be CF manager for 2023-11. > > You probably need some extra admin privileges on your account for accessing > the > CFM functionality, in the meantime I've switched the 202311 CF to InProgress > and marked 202401 as Open. Thanks for taking care of that! (Per the wiki, I requested admin privs on pgsql-www, so still awaiting that)
Re: Commitfest manager November 2023
> On 1 Nov 2023, at 07:33, John Naylor wrote: > > I didn't see any recent mentions in the archives, so I'll volunteer to > be CF manager for 2023-11. You probably need some extra admin privileges on your account for accessing the CFM functionality, in the meantime I've switched the 202311 CF to InProgress and marked 202401 as Open. Thanks for volunteering! -- Daniel Gustafsson
Re: Commitfest manager November 2023
On Wed, Nov 01, 2023 at 01:33:26PM +0700, John Naylor wrote: > I didn't see any recent mentions in the archives, so I'll volunteer to > be CF manager for 2023-11. Thanks, John! -- Michael signature.asc Description: PGP signature
Re: Commitfest manager November 2023
On Wed, Nov 1, 2023 at 7:59 AM Aleksander Alekseev wrote: > Hi, > > > I didn't see any recent mentions in the archives, so I'll volunteer to > > be CF manager for 2023-11. > > I would love to help with that if you need. > > -- > Thanks, > Shihao
Re: Commitfest manager November 2023
Hi, > I didn't see any recent mentions in the archives, so I'll volunteer to > be CF manager for 2023-11. Many thanks for volunteering! If you need any help please let me know. -- Best regards, Aleksander Alekseev
Commitfest manager November 2023
I didn't see any recent mentions in the archives, so I'll volunteer to be CF manager for 2023-11.
Re: Commitfest manager for September
On Wed, Aug 30, 2023 at 2:50 PM Peter Eisentraut wrote: > > On 28.08.23 15:46, Peter Eisentraut wrote: > > I would like to be the commitfest manager for CF 2023-09. > > I think my community account needs to have some privilege change to be > able to act as CF manager in the web interface. Could someone make that > happen? Done! -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
Re: Commitfest manager for September
On 28.08.23 15:46, Peter Eisentraut wrote: I would like to be the commitfest manager for CF 2023-09. I think my community account needs to have some privilege change to be able to act as CF manager in the web interface. Could someone make that happen?
Re: Commitfest manager for September
On Mon, Aug 28, 2023 at 11:42:22AM -0400, Melanie Plageman wrote: > I too had planned to volunteer to help. I volunteer to do a > triage/summary of patch statuses, as has been done occasionally in the > past [1]. > Have folks found this helpful in the past? With the number of patches in place, getting any help with triaging is much welcome, but I cannot speak for Peter. FWIW, with your experience, I think that you are a good fit, as is Aleksander. -- Michael signature.asc Description: PGP signature
Re: Commitfest manager for September
Hi Melanie, On 8/28/23 11:42, Melanie Plageman wrote: I too had planned to volunteer to help. I volunteer to do a triage/summary of patch statuses, as has been done occasionally in the past [1]. Have folks found this helpful in the past? Having a summary to begin with is very helpful for reviewers. Best regards, Jesper
Re: Commitfest manager for September
On Mon, Aug 28, 2023 at 11:36 AM Aleksander Alekseev wrote: > > Hi Peter, > > > I would like to be the commitfest manager for CF 2023-09. > > Many thanks for volunteering! If at some point you will require a bit > of help please let me know. I too had planned to volunteer to help. I volunteer to do a triage/summary of patch statuses, as has been done occasionally in the past [1]. Have folks found this helpful in the past? [1] https://www.postgresql.org/message-id/CAM-w4HOFOUNuOZSpsCfH_ir7dqJNdA1pxkxfaVEvLk5sn6HhsQ%40mail.gmail.com
Re: Commitfest manager for September
Hi Peter, > I would like to be the commitfest manager for CF 2023-09. Many thanks for volunteering! If at some point you will require a bit of help please let me know. -- Best regards, Aleksander Alekseev
Commitfest manager for September
I would like to be the commitfest manager for CF 2023-09.
Re: Commitfest manager for July
On Tue, Jul 4, 2023 at 5:03 AM Michael Paquier wrote: > On Mon, Jul 03, 2023 at 12:26:44PM +0200, Daniel Gustafsson wrote: > > Since this didn't get any takers, and we are in July AoE since a few > days ago, > > I guess I'll assume the role this time in the interest of moving things > along. > > I've switched the 2023-07 CF to in-progress and 2023-09 to open, let's > try to > > close patches! > > Thanks, Daniel! > -- > Michael > If nobody taking that, I can take the responsibility.-- Ibrar Ahmed
Re: Commitfest manager for July
On Mon, Jul 03, 2023 at 12:26:44PM +0200, Daniel Gustafsson wrote: > Since this didn't get any takers, and we are in July AoE since a few days ago, > I guess I'll assume the role this time in the interest of moving things along. > I've switched the 2023-07 CF to in-progress and 2023-09 to open, let's try to > close patches! Thanks, Daniel! -- Michael signature.asc Description: PGP signature
Re: Commitfest manager for July
> On 28 Jun 2023, at 09:45, Daniel Gustafsson wrote: > > A quick scan of the archives doesn't turn up anyone who has volunteered in > advance to run the upcoming commitfest. Is anyone keen at trying their hand > at > this very important community work? The July CF is good for anyone doing this > for the first time IMHO as it's usually less stressful than the ones later in > the cycle. Since this didn't get any takers, and we are in July AoE since a few days ago, I guess I'll assume the role this time in the interest of moving things along. I've switched the 2023-07 CF to in-progress and 2023-09 to open, let's try to close patches! -- Daniel Gustafsson
Commitfest manager for July
A quick scan of the archives doesn't turn up anyone who has volunteered in advance to run the upcoming commitfest. Is anyone keen at trying their hand at this very important community work? The July CF is good for anyone doing this for the first time IMHO as it's usually less stressful than the ones later in the cycle. -- Daniel Gustafsson
Re: Commitfest Manager
On Tue, Feb 21, 2023 at 02:13:08PM -0500, Tom Lane wrote: > Greg Stark writes: >> On Tue, 21 Feb 2023 at 12:29, Tom Lane wrote: >>> Greg Stark writes: >>> We've generally thought that the manager for the last CF of a cycle >>> needs to be someone with experience. > >> Hm. Was that in response to the first paragraph or the second? :) > > The first ;-). Sorry if I wasn't clear. The last CF is the most sensitive one as the feature freeze would happen just around the beginning of April, so the CFM has a bit more pressure in taking the correct decisions, if need be. FYI, I'd prefer spend cycles at patches that could make the cut, rather than doing the classification of the whole. -- Michael signature.asc Description: PGP signature
Re: Commitfest Manager
Greg Stark writes: > On Tue, 21 Feb 2023 at 12:29, Tom Lane wrote: >> Greg Stark writes: >>> Is anyone else itching to be CF manager for March? If anyone new wants >>> to try it out that would be good. >>> >>> Assuming otherwise I'll volunteer. >> We've generally thought that the manager for the last CF of a cycle >> needs to be someone with experience. > Hm. Was that in response to the first paragraph or the second? :) The first ;-). Sorry if I wasn't clear. regards, tom lane
Re: Commitfest Manager
On Tue, 21 Feb 2023 at 12:29, Tom Lane wrote: > > Greg Stark writes: > > Is anyone else itching to be CF manager for March? If anyone new wants > > to try it out that would be good. > > > Assuming otherwise I'll volunteer. > > We've generally thought that the manager for the last CF of a cycle > needs to be someone with experience. Hm. Was that in response to the first paragraph or the second? :) I have experience in years but only limited experience as a commitfest manager. I'm still up for it if you think I'm ready :) -- greg
Re: Commitfest Manager
Greg Stark writes: > Is anyone else itching to be CF manager for March? If anyone new wants > to try it out that would be good. > Assuming otherwise I'll volunteer. We've generally thought that the manager for the last CF of a cycle needs to be someone with experience. regards, tom lane
Commitfest Manager
Is anyone else itching to be CF manager for March? If anyone new wants to try it out that would be good. Assuming otherwise I'll volunteer. -- greg
Re: Commitfest manager for 2022-03
On Mon, 21 Mar 2022 at 21:48, Andres Freund wrote: > > Hi, > > On 2022-02-26 16:12:27 -0500, Greg Stark wrote: > > I do have the time available. What I don't necessarily have is insight > > into everything that needs to be done, especially behind the scenes. > > One thing that desperately needs doing, particularly during the last > commitfest, is looking through CF entries and pruning stuff that shouldn't be > there anymore or that are in the wrong state. Thanks > One can't just automatically mark all failing runs as "waiting on author" > because sometimes there are issues with somebody else posting an incremental > diff confusing cfbot or spurious test failures... What I'm seeing is patches that are failing with either the 027_stream_regress.pl failure that I see is being actively worked on in another thread or simply a timeout which I'm not sure but may be the same issue? But I'll do a pass and then do another pass later in the week when those problems may have been ironed out. -- greg
Re: Commitfest manager for 2022-03
Hi, On 2022-02-26 16:12:27 -0500, Greg Stark wrote: > I do have the time available. What I don't necessarily have is insight > into everything that needs to be done, especially behind the scenes. One thing that desperately needs doing, particularly during the last commitfest, is looking through CF entries and pruning stuff that shouldn't be there anymore or that are in the wrong state. I just went through the list of patches that are failing on http://cfbot.cputube.org/index.html There were several CF entries that haven't made progress in months marked as "needs review", despite the last things on the thread being asks of the author(s). One can't just automatically mark all failing runs as "waiting on author" because sometimes there are issues with somebody else posting an incremental diff confusing cfbot or spurious test failures... If a patch fails to apply and it looks to be a "real patch" clearly some action has to be taken by the author, so marking entries as "waiting on author" is good. Greetings, Andres Freund
Re: Commitfest manager for 2022-03
On Sun, Feb 27, 2022 at 04:51:16PM +0800, Julien Rouhaud wrote: > On Sat, Feb 26, 2022 at 06:37:21PM -0600, Justin Pryzby wrote: > > Can I suggest to update the CF APP to allow: > > | Target version: 16 > > > > I also suggest to update patches to indicate which are (not) being > > considered > > for v15. > > I don't really understand what that field is supposed to mean. It can mean whatever we decide it's convenient for it to mean. I suppose its primary purpose may have been to indicate which backbranch a bugfix applies to (?) I find it useful to indicate whether or not a patch is intended to be considered for the next release. If a patch is targetting v15, it's more interesting to review. @Thomas Munro: I think it'd be useful if cfbot would also show 1) the "target version" (if any); and, 2) whether a patch has a committer set. -- Justin
Re: Commitfest manager for 2022-03
On Sun, Feb 27, 2022 at 11:37 PM Euler Taveira wrote: > > On Sat, Feb 26, 2022, at 9:37 PM, Justin Pryzby wrote: > > |https://commitfest.postgresql.org/37/2906/ > |Row filtering for logical replication > If I'm not wrong, this is merged and should be closed? > > I think Amit forgot to mark it as committed. Done. > I was waiting for some build farm cycles to complete but it is fine to mark it now. -- With Regards, Amit Kapila.
Re: Commitfest manager for 2022-03
On Sat, Feb 26, 2022, at 9:37 PM, Justin Pryzby wrote: > |https://commitfest.postgresql.org/37/2906/ > |Row filtering for logical replication > If I'm not wrong, this is merged and should be closed? I think Amit forgot to mark it as committed. Done. -- Euler Taveira EDB https://www.enterprisedb.com/
Re: Commitfest manager for 2022-03
On Sun, Feb 27, 2022 at 04:51:16PM +0800, Julien Rouhaud wrote: > I don't really understand what that field is supposed to mean. But now that > we're in the final pg15 commit fest, wouldn't it be simpler to actually move > the patches for which there's a agreement that they can't make it to pg15? > Tagging them and letting them rot for a month isn't helpful for the authors or > the CFMs, especially when there are already 250 patches that needs to be > handled. Yes, I don't see any point in having a new tag just to mark patches that will have to be moved to the next CF anyway. These should just be moved to the July one rather than stay in the March one. -- Michael signature.asc Description: PGP signature
Re: Commitfest manager for 2022-03
On Sat, Feb 26, 2022 at 06:37:21PM -0600, Justin Pryzby wrote: > Can I suggest to update the CF APP to allow: > | Target version: 16 > > I also suggest to update patches to indicate which are (not) being considered > for v15. I don't really understand what that field is supposed to mean. But now that we're in the final pg15 commit fest, wouldn't it be simpler to actually move the patches for which there's a agreement that they can't make it to pg15? Tagging them and letting them rot for a month isn't helpful for the authors or the CFMs, especially when there are already 250 patches that needs to be handled. There's already an on-going a discussion for the PGTT patchset, maybe it should also happen for some of the thread you mentioned.
Re: Commitfest manager for 2022-03
Can I suggest to update the CF APP to allow: | Target version: 16 I also suggest to update patches to indicate which are (not) being considered for v15. A few specific ones from myself: |https://commitfest.postgresql.org/37/2573/ |pg_dump - read data for some options from external fileReady for Committer 15 Marked RFC by Daniel Gustafsson since 2021-10-01. Is it more likely than not to be included in v15, or should the "v15" be removed ? |https://commitfest.postgresql.org/37/3499/ |libpq compression Waiting on Author 15 I re-raised the same concerns made ~12 months ago but haven't heard back. WOA since 35 days. Unlikely to be considered/included in v15. |https://commitfest.postgresql.org/37/3571/ |Add LZ4 compression in pg_dump Needs review This patch was just submitted on 2022-02-25. I did a lot of the same things this patch does for a previous patch submission (32/2888) for pg_dump/ZSTD, so I could review this, if there were interest to include it in v15. |https://commitfest.postgresql.org/37/2349/ |Global temporary table Needs review15 The handling/hijacking of pg_class and pg_statistic is not likely to be acceptable. I doubt this will be progressed for v15. |https://commitfest.postgresql.org/37/3448/ |reduce impact of lengthy startup and checkpoint tasks Needs review15 I think this is in the design/concept phase, and not likely for v15, except maybe in reduced scope. |https://commitfest.postgresql.org/37/2906/ |Row filtering for logical replication If I'm not wrong, this is merged and should be closed? For my own patches, it'd be helpful if someone would suggest if any are (not) likely to be progressed for v15. These are marked RFC, but have no "committer" set. Are they all targetting v15? https://commitfest.postgresql.org/37/2863/ Function to log backtrace of postgres processes Ready for Committer Should target v15 ? https://commitfest.postgresql.org/37/2897/ Faster pglz compression Ready for Committer 15 Tomas, are you still planning to merge this one ? https://commitfest.postgresql.org/37/2992/ Allow batched insert during cross-partition updates Ready for Committer https://commitfest.postgresql.org/37/3073/ Add callback table access method to reset filenode when dropping relation Ready for Committer https://commitfest.postgresql.org/37/3384/ use has_privs_for_role for predefined roles Ready for Committer 15 Do all of the RFC patches target v15 (except bugfixes) ? https://commitfest.postgresql.org/37/?status=3 These are not marked as targetting any version .. are any of them being considered for v15 ? https://commitfest.postgresql.org/37/2903/ Parallel Hash Full Join Needs review https://commitfest.postgresql.org/37/3508/ Avoid smgrimmedsync() during index build and add unbuffered IO API Needs review https://commitfest.postgresql.org/37/3182/ automatically generating node support functions Needs review https://commitfest.postgresql.org/37/3183/ Detectable crashes and unlogged table resetsNeeds review Jeff Davis (jdavis) These are set as "targetting v15", but have no committer set. If someone thinks it's unrealistic they'll be included in v15, I suggest to update not to say so. https://commitfest.postgresql.org/37/3272/ Add system view tracking shared buffer actions Needs review15 https://commitfest.postgresql.org/37/3224/ Fix ExecRTCheckPerms() inefficiency with many prunable partitions Needs review15 https://commitfest.postgresql.org/37/3270/ Cache tuple routing info during bulk loads into partitioned tables Needs review15 https://commitfest.postgresql.org/37/3461/ In-place persistence change of a relation (fast ALTER TABLE ... SET LOGGED with wal_level=minimal) Needs review15 https://commitfest.postgresql.org/37/3539/ Allow parallel plan for referential integrity checksNeeds review 15 https://commitfest.postgresql.org/37/3397/ Prefetching in recovery, take IINeeds review15 Thomas Munro (macdice) https://commitfest.postgresql.org/37/2482/ jsonpath syntax extensions Needs review15 https://commitfest.postgresql.org/37/2901/ SQL/JSON: functions Needs review15 https://commitfest.postgresql.org/37/2902/ SQL/JSON: JSON_TABLENeeds review15 https://commitfest.postgresql.org/37/3099/ Asymmetric partition-wise JOIN Needs review15 https://commitfest.postgresql.org/37/3293/ Tags in errordata Needs review15 https://commitfest.postgresql.org/37/3358/ Update relfrozenxmin when
Re: Commitfest manager for 2022-03
On Sat, 26 Feb 2022 at 01:33, Julien Rouhaud wrote: > > On Sat, Feb 26, 2022 at 02:42:33PM +0900, Michael Paquier wrote: > > On Fri, Feb 25, 2022 at 01:58:55PM -0600, David Steele wrote: > > > On 2/25/22 12:39, Greg Stark wrote: > > >> I would like to volunteer. > > > > > I've been hoping somebody would volunteer, so I'm all in favor of you > > > being > > > CF. > > > > Greg as CFM would be fine. It's nice to see someone volunteer. > > +1, thanks a lot Greg! > > Note that the last CF of a major version is probably even more work than > "regular" CF, so if other people are interested there's probably room for > multiple CFMs. I do have the time available. What I don't necessarily have is insight into everything that needs to be done, especially behind the scenes. So if I could have someone to give me tips about things I'm missing or review the things I am doing to see that I've covered everything that would be great. -- greg
Re: Commitfest manager for 2022-03
On Sat, Feb 26, 2022 at 02:42:33PM +0900, Michael Paquier wrote: > On Fri, Feb 25, 2022 at 01:58:55PM -0600, David Steele wrote: > > On 2/25/22 12:39, Greg Stark wrote: > >> I would like to volunteer. > > > I've been hoping somebody would volunteer, so I'm all in favor of you being > > CF. > > Greg as CFM would be fine. It's nice to see someone volunteer. +1, thanks a lot Greg! Note that the last CF of a major version is probably even more work than "regular" CF, so if other people are interested there's probably room for multiple CFMs.
Re: Commitfest manager for 2022-03
On Fri, Feb 25, 2022 at 01:58:55PM -0600, David Steele wrote: > On 2/25/22 12:39, Greg Stark wrote: >> I would like to volunteer. > > Since I've done the March CF for the last seven years, I thought it would be > good if I chimed in. I've been agonizing a bit because I have travel planned > during March and while I *could* do it I don't think I'd be able to do a > good job. That's a time-consuming task, and there have been little occasions to enjoy travelling lately, so have a good time :) > I've been hoping somebody would volunteer, so I'm all in favor of you being > CF. Greg as CFM would be fine. It's nice to see someone volunteer. -- Michael signature.asc Description: PGP signature
Re: Commitfest manager for 2022-03
Hi Greg, On 2/25/22 12:39, Greg Stark wrote: I would like to volunteer. On Fri, 25 Feb 2022 at 05:31, Julien Rouhaud wrote: Is there any volunteer? Since I've done the March CF for the last seven years, I thought it would be good if I chimed in. I've been agonizing a bit because I have travel planned during March and while I *could* do it I don't think I'd be able to do a good job. I've been hoping somebody would volunteer, so I'm all in favor of you being CF. Regards, -David
Re: Commitfest manager for 2022-03
I would like to volunteer. On Fri, 25 Feb 2022 at 05:31, Julien Rouhaud wrote: > > Hi, > > The final commitfest for pg15 will start in a few days, and I didn't see any > discussion on it or anyone volunteering to be a CFM. > > I thought it would be a good idea to send this reminder now and avoid the same > situation as the last commitfest, to avoid unnecessary pain for the CFM(s). > > Is there any volunteer? > > For the record there are already 246 active patches registered. > > -- greg
Commitfest manager for 2022-03
Hi, The final commitfest for pg15 will start in a few days, and I didn't see any discussion on it or anyone volunteering to be a CFM. I thought it would be a good idea to send this reminder now and avoid the same situation as the last commitfest, to avoid unnecessary pain for the CFM(s). Is there any volunteer? For the record there are already 246 active patches registered.
Re: Next Commitfest Manager.
On Thu, Feb 4, 2021 at 1:13 AM Stephen Frost wrote: > Greetings, > > * Ibrar Ahmed (ibrar.ah...@gmail.com) wrote: > > Anyone else already volunteers that? It is my first time so need some > > access, if all agree. > > Thanks for volunteering! > > That said, our last commitfest tends to be the most difficult as it's > the last opportunity for features to land in time for the next major > release and, for my part at least, I think it'd be best to have > someone who has experience running a CF previously manage it. > > To that end, I've talked to David Steele, who has run this last CF for > the past few years and we're in agreement that he's willing to run this > CF again this year, assuming there's no objections. What we've thought > to suggest is that you follow along with David as he runs this CF and > then offer to run the July CF. Of course, we would encourage you and > David to communicate and for you to ask David any questions you have > about how he handles things as part of the CF. This is in line with how > other CF managers have started out also. > As we know July commitfest is coming, I already volunteered to manage that. I did small work with David in the last commitfest and now ready to work on that > > Open to your thoughts, as well as those of anyone else who wishes to > comment. > > Thanks! > > Stephen > -- Ibrar Ahmed
Re: Next Commitfest Manager.
On Thu, Feb 4, 2021 at 2:00 AM David Steele wrote: > On 2/3/21 3:13 PM, Stephen Frost wrote: > > Greetings, > > > > * Ibrar Ahmed (ibrar.ah...@gmail.com) wrote: > >> Anyone else already volunteers that? It is my first time so need some > >> access, if all agree. > > > > Thanks for volunteering! > > > > That said, our last commitfest tends to be the most difficult as it's > > the last opportunity for features to land in time for the next major > > release and, for my part at least, I think it'd be best to have > > someone who has experience running a CF previously manage it. > > > > To that end, I've talked to David Steele, who has run this last CF for > > the past few years and we're in agreement that he's willing to run this > > CF again this year, assuming there's no objections. What we've thought > > to suggest is that you follow along with David as he runs this CF and > > then offer to run the July CF. Of course, we would encourage you and > > David to communicate and for you to ask David any questions you have > > about how he handles things as part of the CF. This is in line with how > > other CF managers have started out also. > > > > Open to your thoughts, as well as those of anyone else who wishes to > > comment. > > +1. This all sounds good to me! > > -- > -David > da...@pgmasters.net Sounds good, I am happy to work with David. -- Ibrar Ahmed
Re: Next Commitfest Manager.
On 2/3/21 3:13 PM, Stephen Frost wrote: Greetings, * Ibrar Ahmed (ibrar.ah...@gmail.com) wrote: Anyone else already volunteers that? It is my first time so need some access, if all agree. Thanks for volunteering! That said, our last commitfest tends to be the most difficult as it's the last opportunity for features to land in time for the next major release and, for my part at least, I think it'd be best to have someone who has experience running a CF previously manage it. To that end, I've talked to David Steele, who has run this last CF for the past few years and we're in agreement that he's willing to run this CF again this year, assuming there's no objections. What we've thought to suggest is that you follow along with David as he runs this CF and then offer to run the July CF. Of course, we would encourage you and David to communicate and for you to ask David any questions you have about how he handles things as part of the CF. This is in line with how other CF managers have started out also. Open to your thoughts, as well as those of anyone else who wishes to comment. +1. This all sounds good to me! -- -David da...@pgmasters.net
Re: Next Commitfest Manager.
Greetings, * Ibrar Ahmed (ibrar.ah...@gmail.com) wrote: > Anyone else already volunteers that? It is my first time so need some > access, if all agree. Thanks for volunteering! That said, our last commitfest tends to be the most difficult as it's the last opportunity for features to land in time for the next major release and, for my part at least, I think it'd be best to have someone who has experience running a CF previously manage it. To that end, I've talked to David Steele, who has run this last CF for the past few years and we're in agreement that he's willing to run this CF again this year, assuming there's no objections. What we've thought to suggest is that you follow along with David as he runs this CF and then offer to run the July CF. Of course, we would encourage you and David to communicate and for you to ask David any questions you have about how he handles things as part of the CF. This is in line with how other CF managers have started out also. Open to your thoughts, as well as those of anyone else who wishes to comment. Thanks! Stephen signature.asc Description: PGP signature
Re: Next Commitfest Manager.
Hi, Anyone else already volunteers that? It is my first time so need some access, if all agree. On Mon, Feb 1, 2021 at 10:17 PM Ibrar Ahmed wrote: > As Commitfest 2021-01 is now closed. I am volunteering to manage next > commitfest. > > > -- > Ibrar Ahmed > -- Ibrar Ahmed
Next Commitfest Manager.
As Commitfest 2021-01 is now closed. I am volunteering to manage next commitfest. -- Ibrar Ahmed
Re: Commitfest manager 2020-11
‐‐‐ Original Message ‐‐‐ On Sunday, October 25, 2020 8:01 PM, Anastasia Lubennikova wrote: > On 20.10.2020 10:30, gkokola...@pm.me wrote: > > > ‐‐‐ Original Message ‐‐‐ > > > > > [snip] > > > Wow, that was well in advance) I am willing to assist if you need any > > > help. > > > > Indeed it was a bit early. I left for vacation after that. For the record, > > I am newly active to the community. In our PUG, in Stockholm, we held a > > meetup during which a contributor presented ways to contribute to the > > community, one of which is becoming CFM. So, I thought of picking up the > > recommendation. > > I have taken little part in CFs as reviewer/author and I have no idea how a > > CF is actually run. A contributor from Stockholm has been willing to mentor > > me to the part. > > Since you have both the knowledge and specific ideas on improving the CF, > > how about me assisting you? I could shadow you and you can groom me to the > > part, so that I can take the lead to a future CF more effectively. > > This is just a suggestion of course. I am happy with anything that can help > > the community as a whole. > > Even though, I've worked a lot with community, I have never been CFM > before as well. So, I think we can just follow these articles: > > https://www.2ndquadrant.com/en/blog/managing-a-postgresql-commitfest/ > https://wiki.postgresql.org/wiki/CommitFest_Checklist > > Some parts are a bit outdated, but in general the checklist is clear. > I've already requested CFM privileges in pgsql-www and I'm going to > spend next week sending pings and updates to the patches at commitfest. Awesome. I will start with requesting the privileges then. > > There are already 219 patches, so I will appreciate if you join me in > this task. Count me in. > > -- > > Anastasia Lubennikova > Postgres Professional: http://www.postgrespro.com > The Russian Postgres Company
Re: Commitfest manager 2020-11
On 20.10.2020 10:30, gkokola...@pm.me wrote: ‐‐‐ Original Message ‐‐‐ [snip] Wow, that was well in advance) I am willing to assist if you need any help. Indeed it was a bit early. I left for vacation after that. For the record, I am newly active to the community. In our PUG, in Stockholm, we held a meetup during which a contributor presented ways to contribute to the community, one of which is becoming CFM. So, I thought of picking up the recommendation. I have taken little part in CFs as reviewer/author and I have no idea how a CF is actually run. A contributor from Stockholm has been willing to mentor me to the part. Since you have both the knowledge and specific ideas on improving the CF, how about me assisting you? I could shadow you and you can groom me to the part, so that I can take the lead to a future CF more effectively. This is just a suggestion of course. I am happy with anything that can help the community as a whole. Even though, I've worked a lot with community, I have never been CFM before as well. So, I think we can just follow these articles: https://www.2ndquadrant.com/en/blog/managing-a-postgresql-commitfest/ https://wiki.postgresql.org/wiki/CommitFest_Checklist Some parts are a bit outdated, but in general the checklist is clear. I've already requested CFM privileges in pgsql-www and I'm going to spend next week sending pings and updates to the patches at commitfest. There are already 219 patches, so I will appreciate if you join me in this task. -- Anastasia Lubennikova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Re: Commitfest manager 2020-11
‐‐‐ Original Message ‐‐‐ > [snip] > > Wow, that was well in advance) I am willing to assist if you need any help. > Indeed it was a bit early. I left for vacation after that. For the record, I am newly active to the community. In our PUG, in Stockholm, we held a meetup during which a contributor presented ways to contribute to the community, one of which is becoming CFM. So, I thought of picking up the recommendation. I have taken little part in CFs as reviewer/author and I have no idea how a CF is actually run. A contributor from Stockholm has been willing to mentor me to the part. Since you have both the knowledge and specific ideas on improving the CF, how about me assisting you? I could shadow you and you can groom me to the part, so that I can take the lead to a future CF more effectively. This is just a suggestion of course. I am happy with anything that can help the community as a whole.
Re: Commitfest manager 2020-11
On 16.10.2020 21:57, Tom Lane wrote: Anastasia Lubennikova writes: On the other hand, I noticed a lot of stall threads, that weren't updated in months. Some of them seem to pass several CFs without any activity at all. I believe that it is wrong for many reasons, the major of which IMHO is a frustration of the authors. Can we come up with something to impove this situation? Yeah, that's a perennial problem. Part of the issue is just a shortage of people --- there are always more patches than we can review and commit in one month. IMO, another cause is that we have a hard time saying "no". If a particular patch isn't too well liked, we tend to just let it slide to the next CF rather than making the uncomfortable decision to reject it. If you've got thoughts about that, or any other ways to improve the process, for sure speak up. From a CFM perspective, we can try the following things: - Write recaps for long-running threads, listing open questions and TODOs. This one is my personal pain. Some threads do look scary and it is less likely that someone will even start a review if they have to catch up with a year-long discussion of 10 people. - Mark patches from first-time contributors with some tag. Probably, these entries are simple/dummy enough to handle them faster. And also it will be a good reminder to be a bit less demanding with beginners. See Dmitry's statistic about how many people have sent patch only once [1]. - Proactively ask committers, if they are going to work on the upcoming CF and will they need any specific help. Maybe we can also ask about their preferred code areas and check what is left uncovered. It's really bad if there is no one, who is working with let's say WAL internals during the CF. TBH, I have no idea, what are we going to do with this knowledge, but I think it's better to know. - From time to time call a council of several committers and make tough decisions about patches that are in discussion for too long (let's say 4 commitfests). Hopefully, it will be easier to reach a consensus in a "real-time" discussion, or we can toss a coin. This problem was raised in previous discussions too [2]. [1] https://www.postgresql.org/message-id/CA+q6zcXtg7cFwX-c+BoOwk65+jtR-sQGZ=1mqg-vgmvzuh8...@mail.gmail.com [2] https://www.postgresql.org/message-id/flat/CAA8%3DA7-owFLugBVZ0JjehTZJue7brEs2qTjVyZFRDq-B%3D%2BNwNg%40mail.gmail.com -- Anastasia Lubennikova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Re: Commitfest manager 2020-11
Anastasia Lubennikova writes: > I was looking for this message, to find out who is the current CFM. > Apparently, the November commitfest is not in progress yet. Nope, nor have we officially appointed a CFM for it yet. We're seldom organized enough to do that much in advance of the CF's start. > Still, I have a question. Should we also maintain statuses of the > patches in the "Open" commitfest? Yes, absolutely, if you notice something out-of-date there, go ahead and fix it. If nothing else, you'll save the eventual CFM some time. > On the other hand, I noticed a lot of stall threads, that weren't > updated in months. Some of them seem to pass several CFs without any > activity at all. I believe that it is wrong for many reasons, the major > of which IMHO is a frustration of the authors. Can we come up with > something to impove this situation? Yeah, that's a perennial problem. Part of the issue is just a shortage of people --- there are always more patches than we can review and commit in one month. IMO, another cause is that we have a hard time saying "no". If a particular patch isn't too well liked, we tend to just let it slide to the next CF rather than making the uncomfortable decision to reject it. If you've got thoughts about that, or any other ways to improve the process, for sure speak up. > P.S. I have a few more ideas about the CF management. I suppose, that > they are usually being discussed at pgcon meetings, but those won't > happen anytime soon. Is there a special place for such discussions, or I > may continue this thread? This thread seems like an OK place for the discussion. As you say, there are not likely to be any in-person meetings for awhile :-( regards, tom lane
Re: Commitfest manager 2020-11
On 24.08.2020 16:08, gkokola...@pm.me wrote: Hi all, Admittedly quite ahead of time, I would like to volunteer as Commitfest manager for 2020-11. If the role is not filled and there are no objections, I can reach out again in October for confirmation. //Georgios Wow, that was well in advance) I am willing to assist if you need any help. I was looking for this message, to find out who is the current CFM. Apparently, the November commitfest is not in progress yet. Still, I have a question. Should we also maintain statuses of the patches in the "Open" commitfest? 21 patches were already committed during this CF, which shows that even "open" CF is quite active. I've updated a few patches, that were sent by my colleagues. If there are no objections, I can do that for other entries too. On the other hand, I noticed a lot of stall threads, that weren't updated in months. Some of them seem to pass several CFs without any activity at all. I believe that it is wrong for many reasons, the major of which IMHO is a frustration of the authors. Can we come up with something to impove this situation? P.S. I have a few more ideas about the CF management. I suppose, that they are usually being discussed at pgcon meetings, but those won't happen anytime soon. Is there a special place for such discussions, or I may continue this thread? -- Anastasia Lubennikova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Commitfest manager 2020-11
Hi all, Admittedly quite ahead of time, I would like to volunteer as Commitfest manager for 2020-11. If the role is not filled and there are no objections, I can reach out again in October for confirmation. //Georgios
Re: BTW, have we got a commitfest manager for the January CF?
On Wed, Jan 09, 2019 at 08:43:08PM -0500, Tom Lane wrote: > I see somebody marked the CF as in-progress, but if anyone volunteered > to be nagger-in-chief for this month, I didn't see that. I'm happy to do it. Would love to chat with recent prior CFMs, if they're willing. Best, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
Re: BTW, have we got a commitfest manager for the January CF?
On Wed, Jan 09, 2019 at 08:43:08PM -0500, Tom Lane wrote: > I see somebody marked the CF as in-progress, but if anyone volunteered > to be nagger-in-chief for this month, I didn't see that. No volunteers as far as I know of... -- Michael signature.asc Description: PGP signature
BTW, have we got a commitfest manager for the January CF?
I see somebody marked the CF as in-progress, but if anyone volunteered to be nagger-in-chief for this month, I didn't see that. regards, tom lane
