tuhaihe opened a new pull request, #119:
URL: https://github.com/apache/cloudberry-backup/pull/119

   Cherry-pick the three commits that have landed on `main` since `REL_2_STABLE`
   was last synced (which is also where `2.2.0-incubating-rc1` is tagged).
   
   - `661c5bab` Update golangci-lint and resolve lint findings. (#114)
   - `d0642705` Fix s3_plugin_e2e: dl.min.io no longer serves MinIO binaries
   - `76e2b8a7` Remove license text from NOTICE
   
   All three apply without conflicts.
   
   The NOTICE change is the reason this matters for the release: Justin Mclean
   raised the NOTICE content during the 2.2.0-rc1 IPMC vote, and rc1 is tagged 
at
   the current `REL_2_STABLE` head, so without this the same issue ships in rc2.
   
   The MinIO fix is also time-sensitive.  `dl.min.io` now returns HTTP 410 for
   every artifact, so the `s3_plugin_e2e` job breaks on its first curl the next
   time it runs on this branch.
   
   One commit on `main` is deliberately **not** included: `deeb0946`
   ("CI: pin Cloudberry branch to `REL_2_STABLE`").  `CLOUDBERRY_REF` is already
   `REL_2_STABLE` here, so the commit reduces to a `TODO: switch back to main 
once
   Cloudberry 3.x stabilizes with PG16` comment, which is a `main`-branch 
concern
   and does not belong on a 2.x release branch.
   
   After this, `REL_2_STABLE` and `main` differ only in the two intentional CI
   divergences: the workflow trigger list includes `REL_2_STABLE`, and the
   `main`-only TODO comment above is absent.
   
   Verified locally on top of `REL_2_STABLE`:
   
   - `go build ./...` and `go vet ./...` clean
   - unit tests pass for backup, restore, utils, history, options, filepath,
     s3plugin and the gpbackman packages
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to