Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

iojs 3.2.0 #43375

Closed
wants to merge 1 commit into from
Closed

iojs 3.2.0 #43375

wants to merge 1 commit into from

Conversation

dunn
Copy link
Contributor

@dunn dunn commented Aug 29, 2015

The repository is now called Node, and the description reads "Future Node.js releases will be from this repo." What's the plan on our end?

@DomT4
Copy link
Member

DomT4 commented Aug 29, 2015

I've been keeping a loose eye on it. From last understanding there was some talk about "Node" becoming a LTS deal, and iojs a more rapid-fire release in line with the current schedule. I don't know how much that has changed. nodejs/node-v0.x-archive#25876 and nodejs/node#2327 go into detail on the upcoming repo merge.

My current thoughts are that once Node/iojs/Nodejs/whatever name is fully compatible with npm we merge iojs into the node formula, delete the iojs formula and support the 0.12.x release of Node in Homebrew/versions as we do the many other older releases. The iojs repo has been renamed at this point, and it looks like the website is due soon as well, so at that point iojs as a name becomes semi-defunct.

@DomT4
Copy link
Member

DomT4 commented Aug 29, 2015

CC @bcomnes, If you wish to comment.

@DomT4
Copy link
Member

DomT4 commented Aug 30, 2015

Feel free to ship this whenever you want by the way Alex. No need to hold on the discussion of names for a little while yet.

@bcomnes
Copy link
Contributor

bcomnes commented Aug 30, 2015

I am on vacation for the next two week and won't be able to put much time in on all of this. So.. by all means do what is necessary!

@DomT4 you have direct contributor access to my fork containing the PR #36369 if you feel that any of that wok is useful (https://github.com/bcomnes/homebrew/tree/tarball is the unfortunately named branch with that work). Feel free to merge, cherry-pick or commit on top of that branch if it helps.

If I have time to contribute, you shall see it in the form of PRs :]

@bcomnes
Copy link
Contributor

bcomnes commented Aug 30, 2015

Just to reconfirm my understanding:

The next version of node (beyond 0.12) will be called node, and will actually be made up of current iojs and node 0.12 work.

Its not quite out yet, so no action needs to be taken at the moment. I imagine the current node formula will be a version bump and possibly some minor modifications.

It is my understanding iojs will remain around following a more rapid release schedule. Maybe this can be the node formula's devel option? Maybe just have a separate, but incompatible iojs formula as we do now?

Finally, the point of contention, the floating patches still may be in place when all of this happens.

My guess is that it will just come down to waiting and seeing what actually happens before any concrete plan can be put together wrt formula modifications.

@dunn dunn closed this in 87db7b6 Aug 30, 2015
@mgol
Copy link

mgol commented Aug 30, 2015

I don't think anything will be called io.js after Node v4 comes out. The release cycle will be slower: a stable release every 6 months, not weeks but there will be canary "alpha" releases always on latest stable V8 like io.js today is.

io.js is no more.

@bcomnes
Copy link
Contributor

bcomnes commented Aug 30, 2015

mzgol, that is very much a possibility as well. Do you know of any links to discussions or announcements on the matter of naming after the merge?

@dunn dunn deleted the iojs branch August 30, 2015 15:12
@mgol
Copy link

mgol commented Aug 30, 2015

Only this but the difference in naming has caused many problems for io.js so I can't imagine they'd keep it on master which is used to prepare for future releases.

ybogdanov pushed a commit to ybogdanov/homebrew that referenced this pull request Sep 1, 2015
@Homebrew Homebrew locked and limited conversation to collaborators Jul 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants