Feedback-ID: ie0a040ee:Fastmail
Message-ID: <89f5e690-1e4b-4b55-96d3-0b6f771523a6@eisentraut.org>
Date: Sun, 2 Mar 2025 18:10:37 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: branching soon
From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-translators@lists.postgresql.org
References: <3f0c0de4-cf93-48a4-955f-ec59797d477d@eisentraut.org>
 <41a0ebc8-1417-4dac-ae19-068e10a89f4a@eisentraut.org>
Content-Language: en-US
In-Reply-To: <41a0ebc8-1417-4dac-ae19-068e10a89f4a@eisentraut.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/89f5e690-1e4b-4b55-96d3-0b6f771523a6%40eisentraut.org>
Precedence: bulk

On 27.02.25 11:28, Peter Eisentraut wrote:
> On 24.02.25 11:14, Peter Eisentraut wrote:
>> Hopefully, we're done with releases and re-releases for now.  So now I 
>> would like to do the translations branching soon.  We did it around 
>> this time last year, which I think worked fine.
>>
>> One reason I would like to move forward with this soon is that I would 
>> like to get <https://commitfest.postgresql.org/patch/5429/> committed 
>> and run it through the whole pipeline before feature freeze.
>>
>> Unless there are any concerns, I will do this later this week.
> 
> This has been done.  Be sure to adjust your local checkouts as appropriate.

It looks like I created the branch wrong (at a wrong branch point), so I 
had to delete it and recreate it again.  So you'll probably get some 
kind of error if you git pull your REL_17_STABLE checkout.  Sorry about 
that.

Also, there had been a couple of commits to the (now deleted) 
REL_17_STABLE that synced the translations with the wrong upstream.  So 
those are probably no longer necessary.