mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1876] Release 1.91 #956
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#956
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gaul on GitHub (Jan 28, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1876
Ubuntu 22.04 (2022-04-21) and Fedora 36 (2022-04-19) will release soon. We should try to release 1.91 soon to allow distros time to upgrade. We may want to defer some risky PRs until 1.92. Currently merged commits:
https://github.com/s3fs-fuse/s3fs-fuse/compare/v1.90...master
@ggtakec commented on GitHub (Jan 29, 2022):
I would like to include #1877 in 1.91.
#1802 can be postponed after the 1.91 release.
What about #1823?
Since it is a specialized part for CEPH, I think it is possible to merge at this release.
@rainmeng commented on GitHub (Feb 22, 2022):
Hi Team,
Any updates to this one? We're waiting for a few important fixes - right now they're in master branch only.
Best,
Ran
@rainmeng commented on GitHub (Feb 22, 2022):
Suggest to include
github.com/s3fs-fuse/s3fs-fuse@9d1552a54ewhich is crucial to enable AWS EC2 IMDSv2.
@juliogonzalez commented on GitHub (Mar 8, 2022):
Git repo for all RPM distributions
https://github.com/juliogonzalez/s3fs-fuse-rpm/pull/20 merged and released
openSUSE RPMs
https://build.opensuse.org/request/show/960279
On accepted, it will go into Tumbleweed, and then into the next Leap version after 15.4)
Fedora and EPEL RPMs
@ggtakec commented on GitHub (Mar 8, 2022):
@juliogonzalez Thanks!