Re: a few thoughts on the schedule

On Wed, May 13, 2015 at 8:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>
> > I am already concerned about some of the commits that have gone in
> > very recently, particularly these:
>
> There is going to need to be a mop-up period, and we ought to be willing
> to revert anything we feel wasn't really ready. I don't feel that those
> decisions need to be made in a hurry though. I'm envisioning taking about
> a month to look more closely at committed patches and see what needs to be
> cleaned up or undone altogether.
>

I think doing post-commit review is really a good thing especially for
the patches which have more impact. One way to achieve could be
that we can identify all the patches that can have high impact (at least
feature patches, it shouldn't be difficult to identify such patches) and
some of the senior members like you can review them thoroughly after
the feature freeze (at end of development cycle), ofcourse it is better
if that can be done during development, but it seems that doesn't happen
many of the times. So if we add a phase after feature freeze and before
first release of the version, that can avoid some serious problems that
the project faces during beta or post release.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com