mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #423] new 1.80 release? #227
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#227
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 @mapreri on GitHub (May 26, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/423
what do you think about cutting a new release? with 200+ commits since the last one and many fixes I guess it's getting overdue 😉
@ggtakec commented on GitHub (May 29, 2016):
Hi @mapreri
Since the issues has been settled, I also was thinking that we should be the new release.
I will prepare a new release after confirming the last PR.
Please wait just a little bit later.
In the future, I would like to regularly release on a quarterly basis other than the patch release by the fatal problem.
Thanks for your help.
Takeshi.
@ggtakec commented on GitHub (May 29, 2016):
@mapreri
I made new release tag v1.80 and changed some files(ChangeLog and configure.ac) for new release.
Please checkout it and build new package.
Thanks in advance for your assistance.
@gaul commented on GitHub (May 29, 2016):
👍 Quarterly releases.
@mapreri commented on GitHub (May 29, 2016):
Great! Thank you! 😄
@jollyroger do you think you can update the debian package for this? ^^
@mapreri commented on GitHub (Jun 12, 2016):
[OT, but doesn't deserve a bug]
btw, the copyright headers on the file needs some love: your copyright (according to those headers) is still only for 2007-2013 :)
@ggtakec commented on GitHub (Jun 14, 2016):
@mapreri Thank you for your notice.
Until the next release, I am going to change the Copyright of the source code header in the following format in order not to edit by each of the new year:
Copyright (c) [year] [name]
Thanks for your kindness.
@ggtakec commented on GitHub (May 7, 2017):
Fixed format for year part of copyright by #587