mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #586] Preparation for release of version 1.81 #332
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#332
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 @ggtakec on GitHub (May 7, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/586
Additional Information
n/a
Details about issue
We will prepare for the release of the new version 1.81.
@ggtakec commented on GitHub (May 13, 2017):
Launched new release 1.81 now.
@andrewgaul @orozery @driskell @liuyuhong66 @Vascom @hudsantos @kasbah @treestem @deepeeess @tlevi @sqlbot
Your help was much appreciated. I could not have done this new release without you.
@mapreri @jollyroger
Just let you know, new release 1.81 version is tagged now.
Please check and start to package it if it have no problem.
Thanks in advance for your assistance.
@ggtakec commented on GitHub (May 13, 2017):
@mapreri @jollyroger
I'm sorry for my fault that had a problem that should not be included.
Thus I will push new tag(version) 1.82 soon, please not package as 1.81, and do 1.82 after that.
Regards,
@ggtakec commented on GitHub (May 13, 2017):
I rushed and tagged version 1.82.(for version 1.81 is not used)
@andrewgaul @sqlbot
Thank you for pointing out security issues.
@mapreri @jollyroger
Please check 1.82(not 1.81) and try to packge it.
If you find any problem, please let me know.
Regards,
@jollyroger commented on GitHub (May 15, 2017):
@ggtakec thank you! I'll try it and let you know.
@ggtakec commented on GitHub (May 16, 2017):
@jollyroger Thanks for all, I am looking forward to your reply.
Regards,
@mapreri commented on GitHub (Jun 23, 2017):
@jollyroger any news? :)