| From: | Jacob Champion <pchampion(at)vmware(dot)com> |
|---|---|
| To: | "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "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 20:49:12 |
| Message-ID: | 742abea309d121139d63d89f58a6b9ed9ade7919.camel@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Thu, 2021-09-16 at 15:59 -0400, Tom Lane wrote:
> Jacob Champion <pchampion(at)vmware(dot)com> writes:
> > 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?
>
> This would be the right list to ask for that, I think. -hackers doesn't
> deal in website issues.
Cool. Consider this a feature request, then, to have dev snapshots for
every STABLE branch, even during beta periods, for CIs that are
watching the latest development state and want to be handed a tarball
rather than git-clone. (It's not a big deal in the end, just an
annoyance.)
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-09-17 09:28:38 | Re: Publishing 14 source snapshots? |
| Previous Message | Tom Lane | 2021-09-16 19:59:22 | Re: Publishing 14 source snapshots? |