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

Status of v0.8.x? #30

Closed
chorrell opened this issue Aug 6, 2015 · 3 comments
Closed

Status of v0.8.x? #30

chorrell opened this issue Aug 6, 2015 · 3 comments

Comments

@chorrell
Copy link

chorrell commented Aug 6, 2015

Hi!

Apologies if this has already been covered elsewhere. I'm going on the assumption that support (e.g., security fixes) for v0.8.x will be dropped (unless that's happened already?) I can't find any explicit statement about this anywhere, but it seems to be the case and it's not included as an LTS release (which is good!).

I'm asking because I want to know if and when I can stop including a v0.8.x in the Docker node image (nodejs/docker-node#34). It should be noted that once dropped, users would still be able to pull a node v0.8.x image from the registry (e.g, docker pull node:0.8.28 or docker pull node:0.8) there just won't be any 0.8 updates once I drop it from the GitHub repo.

@bnoordhuis
Copy link
Member

I'm going on the assumption that support (e.g., security fixes) for v0.8.x will be dropped (unless that's happened already?)

I believe that's the case, the last v0.8 release was over a year ago. v0.8 wasn't discussed in any of the LTS discussions either, as far as I'm aware.

@Fishrock123
Copy link
Member

Yeah, as far as I am aware 0.8 had already been put to rest once 0.12 came out.

@chorrell
Copy link
Author

chorrell commented Aug 6, 2015

OK cool. I'll make plans to eventually drop if from the docker-node image.

Thanks!

@jasnell jasnell closed this as completed Oct 16, 2015
balupton added a commit to balupton/Release that referenced this issue Oct 26, 2020
Dates pulled from:

- nodejs#30
- https://nodejs.org/dist/v0.8.0/
- https://nodejs.org/dist/v0.10.0/

Reasoning is that I have an automated maintenance suite for my 100+ packages that has been updated to use this schedule to determine support for node.js versions (and will generate compiled code for each node version the package intends to support) - some utility packages go back to node v0.8 - as such rather than manually adjusting the results I receive from this, I would rather just add the details here.
BethGriggs pushed a commit that referenced this issue Nov 6, 2020
Dates pulled from:

- #30
- https://nodejs.org/dist/v0.8.0/
- https://nodejs.org/dist/v0.10.0/

Reasoning is that I have an automated maintenance suite for my 100+ packages that has been updated to use this schedule to determine support for Node.js versions (and will generate compiled code for each node version the package intends to support) - some utility packages go back to node v0.8 - as such rather than manually adjusting the results I receive from this, I would rather just add the details here.
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

No branches or pull requests

4 participants