Re: Git tag for v15

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Nemo <me(at)captnemo(dot)in>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Git tag for v15
Date: 2022-10-13 14:06:53
Message-ID: 953878.1665670013@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> If for whatever reason a problem is found before the tag has been
> posted, then a new Git commit is chosen and a new tarball published.
> The tag will then match the new commit, not the original obviously.
> I don't know what would happen if a problem were to be found *after* the
> tag has been pushed; normally that would just mean the fix would have to
> wait until the next minor version in that branch. It would have to be
> something really serious in order for this process to be affected.
> As far as I know, this has never happened.

I don't think it's happened since we adopted Git, anyway. The plan
if we did have to re-wrap at that point would be to increment the version
number(s), since not doing so would probably create too much confusion
about which tarballs were the correct ones.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-10-13 14:08:30 Re: Move backup-related code to xlogbackup.c/.h
Previous Message Robert Haas 2022-10-13 14:05:06 Re: Move backup-related code to xlogbackup.c/.h