[GH-ISSUE #206] Release 1.79 #117

New issue

Closed

opened 2026-03-04 01:42:15 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 01:42:15 +03:00

Owner

Originally created by @gaul on GitHub (Jul 7, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/206

s3fs has many commits since last September: https://github.com/s3fs-fuse/s3fs-fuse/compare/v1.78...master

including support for V4 signing, GovCloud, xattrs, special characters, and fixing many bugs including a data corruption issue #64. The only blocking issue I see is #203 which could change the format of extended attributes.

Originally created by @gaul on GitHub (Jul 7, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/206 s3fs has many commits since last September: https://github.com/s3fs-fuse/s3fs-fuse/compare/v1.78...master including support for V4 signing, GovCloud, xattrs, special characters, and fixing many bugs including a data corruption issue #64. The only blocking issue I see is #203 which could change the format of extended attributes.

kerem closed this issue

2026-03-04 01:42:16 +03:00

kerem commented

2026-03-04 01:42:16 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 9, 2015):

@andrewgaul
I am also want to as soon as possible for the next version release.
There is also Issue of still being confirmed (no reply), I was hesitant.
Because it is a new problem also it seems like does not occur, so that I will make new release at this weekend.
About #203, if it need to change format, it will fix next release after v1.79.
If you have a problem, please let me know.
Regards,

@ggtakec commented on GitHub (Jul 9, 2015): @andrewgaul I am also want to as soon as possible for the next version release. There is also Issue of still being confirmed (no reply), I was hesitant. Because it is a new problem also it seems like does not occur, so that I will make new release at this weekend. About #203, if it need to change format, it will fix next release after v1.79. If you have a problem, please let me know. Regards,

kerem commented

2026-03-04 01:42:17 +03:00

Author

Owner

@kahing commented on GitHub (Jul 9, 2015):

If #203 changes the format, doesn't it make sense to fix it before the next release, so that s3fs doesn't behave differently across versions? Otherwise people upgrading from 1.79 to the next version will have problems.

@kahing commented on GitHub (Jul 9, 2015): If #203 changes the format, doesn't it make sense to fix it before the next release, so that s3fs doesn't behave differently across versions? Otherwise people upgrading from 1.79 to the next version will have problems.

kerem commented

2026-03-04 01:42:17 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 11, 2015):

@kahing
I think we can keep compatibility between v1.79 and the newer version which is changed about xattr http header if it is needed.

About #203, I think it does not need to change the header name for xattr, because s3cmd and AWS console should modify x-amz-meta-xattr header if user need to change.
For details, I will comment on #203 issue.

So I would make new release because we can keep compatibility regardless of the result of #203.

Thanks a lot.

@ggtakec commented on GitHub (Jul 11, 2015): @kahing I think we can keep compatibility between v1.79 and the newer version which is changed about xattr http header if it is needed. About #203, I think it does not need to change the header name for xattr, because s3cmd and AWS console should modify x-amz-meta-xattr header if user need to change. For details, I will comment on #203 issue. So I would make new release because we can keep compatibility regardless of the result of #203. Thanks a lot.

kerem commented

2026-03-04 01:42:17 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 12, 2015):

Hi, all
I wait to build v1.79 release until #203 issue is resolved.
Regards,

@ggtakec commented on GitHub (Jul 12, 2015): Hi, all I wait to build v1.79 release until #203 issue is resolved. Regards,

kerem commented

2026-03-04 01:42:17 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 19, 2015):

Hi, all
Uploaded new release v1.79.
If you found a problem and issues, please post new issue.

Thanks in advance for your assistance.

@ggtakec commented on GitHub (Jul 19, 2015): Hi, all Uploaded new release v1.79. If you found a problem and issues, please post new issue. Thanks in advance for your assistance.