On 20 September 2021 6:55:20 pm IST, Abraham Raji
<abrahamrajione@gmail.com> wrote:
>>So if you really want to go ahead with the update, make sure
gitlab is not
>> broken with the new version.
>So I should build the current version of Gitlab from the
>fast-track/experimental
>repo with the updated version of the gem. Is that right?
>
>If the gem breaks the current version of Gitlab do we fix it or
upload it
>together with
>Gitlab 14.1.5 update?
The problems were,
1. You did not target experimental, which is always safer for
potentially breaking changes (minor 0.x updates)
2. You did not mention the update was for gitlab 14.1 in rfs mail.
Uploading to experimental should be fine if the version in
unstable works with existing gitlab version. But if the old version
itself need the version from experimental, we upload first to
personal repos and update everything together.
--
Sent from my Android device with K-9 Mail. Please excuse my
brevity.