待辦事項 #44056

Update S3_0 msys2 environment

啟用日期: 2022-03-08 23:18 最後更新: 2022-06-14 08:22

回報者:
負責人:
類型:
狀態:
關閉
里程碑:
優先權:
5 - 中
嚴重程度:
5 - 中
處理結果:
修正
檔案:
2

細節

We are likely to update msys2 environment of S3_0 during its lifetime. Most probable around the time 3.1.0-beta1 gets released, and with the same environment version.

One thing that we may need to port to S3_0 before we can update the msys2 environment is localization fix #44047.

Ticket History (3/9 Histories)

2022-03-08 23:18 Updated by: cazfi
  • New Ticket "Update S3_0 msys2 environment" created
2022-03-16 12:14 Updated by: cazfi
評語

Attached patch makes it possible to use msys2-220309 with S3_0. Not meant for committing, but just available for developers who want to use newer environment.

2022-04-25 06:35 Updated by: cazfi
評語

As noted in #44286, msys2 upstream will bump their minimum requirement to Windows-8.1, and we can't take that to S3_0. So any update of S3_0 msys2 update needs to be to a version earlier than their req bump. At this point I assume it to mean that we will do the update to 3.0.3 (can't leave later, we don't want to do it unnecessarily early)

2022-05-27 11:57 Updated by: cazfi
評語

Likely we have two iterations of this during the 3.0.3 cycle. As soon as 3.0.2 has been released, we can set S3_0 to use what ever msys2 environment we have for S3_1/master at the time. Then we make the final msys2 environment later during the cycle.

2022-05-31 06:11 Updated by: cazfi
評語

Reply To cazfi

As soon as 3.0.2 has been released, we can set S3_0 to use what ever msys2 environment we have for S3_1/master at the time.

Update for S3_1/master coming in #43947 - even if that's not ready by 3.0.2 release, we may want to wait for it for S3_0 too.

2022-06-08 10:47 Updated by: cazfi
  • 負責人 Update from (無) to cazfi
  • 處理結果 Update from to Accepted
2022-06-14 08:22 Updated by: cazfi
  • 狀態 Update from 開啟 to 關閉
  • 處理結果 Update from Accepted to 修正

編輯

Please login to add comment to this ticket » 登入