| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Mitar <mmitar(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: commitfest: When are you assigned patches to review? |
| Date: | 2019-01-08 09:14:10 |
| Message-ID: | alpine.DEB.2.21.1901081011400.32421@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Mitar,
> I am new to this community. I have submitted few patches to this
> commitfest and I have read that it is expected that I also review some
> other patches. But I am not sure about the process here. Should I wait
> for some other patches to be assigned to me to review? Or is there
> some other process?
The process is that *you* choose the patches to review and register as
such for the patch on the CF app.
> Also, how is the level at which I should review it
> determined?
Patches as complex as the one you submitted?
Based on your area of expertise?
> I am not really too sure in my skills and understanding of
> PostgreSQL codebase to feel confident that I can review well, but I am
> willing to try. I have read [1] and [2].
There are doc patches, client-side code patches, compilation
infrastructure patches...
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2019-01-08 09:50:39 | Re: Fast path for empty relids in check_outerjoin_delay() |
| Previous Message | Jamison, Kirk | 2019-01-08 09:07:09 | RE: Cache relation sizes? |