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

fedora 25! #579

Closed
jbergstroem opened this issue Dec 21, 2016 · 11 comments
Closed

fedora 25! #579

jbergstroem opened this issue Dec 21, 2016 · 11 comments
Labels

Comments

@jbergstroem
Copy link
Member

Almost a month old. Kid grew up quick!

Seeing how fedora22 eol'ed in july, how about we retire it while introducing 25?

@gibfahn
Copy link
Member

gibfahn commented Dec 22, 2016

+1 to retiring fedora 22 if it's been EOL for 6 months. Does that mean it won't be supported in 8 (so it will be supported until v6 EOL)?

@jbergstroem
Copy link
Member Author

Since this is still floating I'm not sure how we'll handle 'official' support: nodejs/node#8922

@jbergstroem
Copy link
Member Author

Also, I don't think we are specific in terms of os'es we support or don't other than what we build against.

@jbergstroem
Copy link
Member Author

I have two vm's on rackspace running; worked fine with the current refactor. Attaching them to jenkins tomorrow!

@jbergstroem
Copy link
Member Author

build just passed: https://ci.nodejs.org/job/node-test-commit-linux/nodes=fedora25-x64/6938/

Does anyone object against retiring 22? No document to update in main repo, so to speak..

@jbergstroem
Copy link
Member Author

@jbergstroe said:
Does anyone object against retiring 22? No document to update in main repo, so to speak..

Actually, let me check with libuv first..

@jbergstroem
Copy link
Member Author

jbergstroem commented Dec 27, 2016

ping @saghul, @bnoordhuis, @indutny, ?

@saghul
Copy link
Member

saghul commented Jan 2, 2017

No objections from me!

@bnoordhuis
Copy link
Member

Likewise.

@jbergstroem
Copy link
Member Author

Cool. I'll go ahead and retire fedora 22 shortly then.

@maclover7
Copy link
Contributor

22 has been removed from ci.nodejs.org as far as I can see, 25 has been added, so I think this is done now. Going to give this a close, please reopen if necessary.

maclover7 added a commit to maclover7/build that referenced this issue Jan 2, 2018
Machines do not appear in https://ci.nodejs.org/computer, or in
`ansible/inventory.yml`.

Refs: nodejs#579
Refs: nodejs#688
maclover7 added a commit to maclover7/build that referenced this issue Jan 3, 2018
Machines do not appear in https://ci.nodejs.org/computer, or in
`ansible/inventory.yml`.

Refs: nodejs#579
Refs: nodejs#688
maclover7 added a commit to maclover7/build that referenced this issue Jan 3, 2018
Machines do not appear in https://ci.nodejs.org/computer, or in
`ansible/inventory.yml`.

Refs: nodejs#579
Refs: nodejs#688
maclover7 added a commit that referenced this issue Jan 3, 2018
Machines do not appear in https://ci.nodejs.org/computer, or in
`ansible/inventory.yml`.

PR-URL: #1063
Reviewed-By: Rod Vagg <rod@vagg.org>
Refs: #579
Refs: #688
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants