Re: PG compilation error with Visual Studio 2015/2017/2019
От | Amit Kapila |
---|---|
Тема | Re: PG compilation error with Visual Studio 2015/2017/2019 |
Дата | |
Msg-id | CAA4eK1LpH4hhfK9O2Gvd1Cy20RekoDaFK72CW_-Bi4WUK+Nxyw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PG compilation error with Visual Studio 2015/2017/2019 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: PG compilation error with Visual Studio 2015/2017/2019
|
Список | pgsql-hackers |
On Thu, May 7, 2020 at 6:51 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Amit Kapila <amit.kapila16@gmail.com> writes: > > On Thu, May 7, 2020 at 11:57 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> Monday is a back-branch release wrap day. > > > How can I get the information about release wrap day? The minor > > release dates are mentioned on the website [1], but this information > > is not available. Do we keep it some-fixed number of days before > > minor release? > > Yes, we've been using the same release schedule for years. The > actual tarball wrap is always on a Monday --- if I'm doing it, > as is usually the case, I try to get it done circa 2100-2300 UTC. > There's a "quiet period" where we discourage nonessential commits > both before (starting perhaps on the Saturday) and after (until > the releases are tagged in git, about 24 hours after wrap). > The delay till public announcement on the Thursday is so the > packagers can produce their builds. Likewise, the reason for > a wrap-to-tag delay is in case the packagers find anything that > forces a re-wrap, which has happened a few times. > Now that branches are tagged, I would like to commit and backpatch this patch tomorrow unless there are any more comments/objections. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: