Re: Publishing 14 source snapshots?

From: Jacob Champion <pchampion(at)vmware(dot)com>
To: "adrian(dot)klaver(at)aklaver(dot)com" <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org>
Subject: Re: Publishing 14 source snapshots?
Date: 2021-09-16 18:09:18
Message-ID: c8381074e2e0eecef76be96df09d3a8c72a6fc12.camel@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Thu, 2021-09-16 at 10:50 -0700, Adrian Klaver wrote:
> On 9/16/21 9:41 AM, Jacob Champion wrote:
> > On Thu, 2021-09-16 at 09:12 -0700, Adrian Klaver wrote:
> > > 14 is in Beta:
> >
> > Yep, we've been using those artifacts for now as a workaround. In our
> > case, it'd be nice to have daily snapshots for the 14 stable branch
>
> I knew there was an explanation for this, see here:
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.postgresql.org%2Fdownload%2Fsnapshots%2F&amp;data=04%7C01%7Cpchampion%40vmware.com%7C6b54f08db86b436a555b08d9793a7ed5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637674114423690457%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=I4oJOoV796iFyeFPmPSOwT%2BSvzAptf1B1CQe3usIjEI%3D&amp;reserved=0
>
> "Beta and Release Candidate packages are built prior to the release of
> new major versions of PostgreSQL. They are not built continually."

Right -- I'd assumed that was because pg_upgrade has to support betas
and RCs, so it's useful to have defined points in time for official
support. In our case, we don't want the "official" builds; we just want
to track the 14 branch, similar to the way we can track the dev (15)
snapshot folder.

> There are also "branch tip" snapshots
> built from all supported stable branches, which contains all bugfixes
> that are scheduled for the next release. "

This is the sentence that seemed to cover it for me -- I thought 14
would be considered one of the stable branches for which snapshots
would be useful, even during beta.

> You could go here:
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpostgres%2Fpostgres&amp;data=04%7C01%7Cpchampion%40vmware.com%7C6b54f08db86b436a555b08d9793a7ed5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637674114423690457%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=1sUIhEDvtRsmD8EzqtI5zd4rOmc7rBfNZUVr80GfB1o%3D&amp;reserved=0
>
> and grab the REL_14_STABLE branch.

Absolutely -- this isn't a hard blocker for us; it's just a special
case in our CI that I'd rather didn't exist... Maybe it'd be worthwhile
to ask on -hackers for an update to the snapshot policy?

Thanks,
--Jacob

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2021-09-16 19:59:22 Re: Publishing 14 source snapshots?
Previous Message Adrian Klaver 2021-09-16 17:50:36 Re: Publishing 14 source snapshots?