Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove retract directive #400

Closed
wants to merge 1 commit into from
Closed

Remove retract directive #400

wants to merge 1 commit into from

Conversation

y-yagi
Copy link

@y-yagi y-yagi commented Oct 2, 2021

What does this pull request do?

Remove retract directive.

The retract directive only works Go >= 1.16. The versions under that can't recognize the directive and cause an error. (e.g. https://github.com/fsnotify/fsnotify/runs/3414923756)

So removed the directive to work builds.

Where should the reviewer start?

Please see CI passes.

How should this be manually tested?

No need.

The `retract` directive only works Go >= 1.16.
The versions under that can't recognize the directive and cause an error.
(e.g. https://github.com/fsnotify/fsnotify/runs/3414923756)

So removed the directive to work builds.
@shogo82148
Copy link
Member

The latest version of Go is 1.17.5, and supported versions of Go are 1.17.5 and 1.16.12.
https://go.dev/doc/devel/release#policy

Go 1.15 and older are already unsupported.
Should we drop support of them?

@nathany
Copy link
Contributor

nathany commented Jan 14, 2022

@y-yagi Thanks for bringing this up, but I agree with @shogo82148 -- we should only need to support just the last 2 versions of Go.

Also, fsnotify 1.5.0 had a number of regressions, so I think it's important to prevent people from using it.
#390 #393 #389.

@nathany nathany closed this Jan 14, 2022
arp242 added a commit that referenced this pull request Feb 9, 2023
I have no idea if anyone is using Go 1.16 with fsnotify.

Go 1.16 (released August 2021) became mandatory with v1.5.1 (August
2021). Go 1.17 was released just a few days before it was tagged. Some
people did experience problems (#400), but overall the feedback was
limited.

So based on this, I think it's probably safe to just follow the Go
release policy: "Each major Go release is supported until there are two
newer major releases."

This will allow merging #554
arp242 added a commit that referenced this pull request Feb 9, 2023
I have no idea if anyone is using Go 1.16 with fsnotify.

Go 1.16 (released August 2021) became mandatory with v1.5.1 (August
2021). Go 1.17 was released just a few days before it was tagged. Some
people did experience problems (#400), but overall the feedback was
limited.

So based on this, I think it's probably safe to just follow the Go
release policy: "Each major Go release is supported until there are two
newer major releases."

This will allow merging #554
@arp242 arp242 mentioned this pull request Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants