Schedule of commit fests for PG14

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Schedule of commit fests for PG14

Michael Paquier-2
Hi all,

Normally $subject would have been discussed at the developer meeting
in Ottawa, but that's not going to happen per the current situation.

For the last couple of years, we have been using the same timeline for
for commit fests in a development cycle, so why not going with the
same flow this year?  This would mean 5 CFs:
- 2020-07-01~2020-07-31
- 2020-09-01~2020-09-30
- 2020-11-01~2020-11-30
- 2021-01-01~2021-01-31
- 2021-03-01~2021-03-31

Any thoughts or opinions?

Thanks,
--
Michael

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Schedule of commit fests for PG14

Julien Rouhaud
On Thu, May 21, 2020 at 8:36 AM Michael Paquier <[hidden email]> wrote:

>
> Hi all,
>
> Normally $subject would have been discussed at the developer meeting
> in Ottawa, but that's not going to happen per the current situation.
>
> For the last couple of years, we have been using the same timeline for
> for commit fests in a development cycle, so why not going with the
> same flow this year?  This would mean 5 CFs:
> - 2020-07-01~2020-07-31
> - 2020-09-01~2020-09-30
> - 2020-11-01~2020-11-30
> - 2021-01-01~2021-01-31
> - 2021-03-01~2021-03-31
>
> Any thoughts or opinions?

+1, I don't see for now any reason not going with the same planning for pg14.


Reply | Threaded
Open this post in threaded view
|

Re: Schedule of commit fests for PG14

Tom Lane-2
In reply to this post by Michael Paquier-2
Michael Paquier <[hidden email]> writes:
> Normally $subject would have been discussed at the developer meeting
> in Ottawa, but that's not going to happen per the current situation.

> For the last couple of years, we have been using the same timeline for
> for commit fests in a development cycle, so why not going with the
> same flow this year?  This would mean 5 CFs:
> - 2020-07-01~2020-07-31
> - 2020-09-01~2020-09-30
> - 2020-11-01~2020-11-30
> - 2021-01-01~2021-01-31
> - 2021-03-01~2021-03-31

Yeah, nobody's expressed any great unhappiness with the schedule
recently, so let's just do the same thing again this year.

                        regards, tom lane


Reply | Threaded
Open this post in threaded view
|

Re: Schedule of commit fests for PG14

David Steele
In reply to this post by Michael Paquier-2
On 5/21/20 2:35 AM, Michael Paquier wrote:

> Hi all,
>
> Normally $subject would have been discussed at the developer meeting
> in Ottawa, but that's not going to happen per the current situation.
>
> For the last couple of years, we have been using the same timeline for
> for commit fests in a development cycle, so why not going with the
> same flow this year?  This would mean 5 CFs:
> - 2020-07-01~2020-07-31
> - 2020-09-01~2020-09-30
> - 2020-11-01~2020-11-30
> - 2021-01-01~2021-01-31
> - 2021-03-01~2021-03-31
>
> Any thoughts or opinions?

+1. This schedule seems to have worked fine the last two years.

Regards,
--
-David
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Schedule of commit fests for PG14

Michael Paquier-2
On Thu, May 21, 2020 at 10:13:41AM -0400, David Steele wrote:
> +1. This schedule seems to have worked fine the last two years.

Sounds like a conclusion to me.  I have created four new CFs for the
next development cycle then in the CF app.
--
Michael

signature.asc (849 bytes) Download Attachment