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

[email protected] -> [email protected] changelog #339

Closed
29 tasks
rvagg opened this issue Jan 13, 2015 · 11 comments
Closed
29 tasks

[email protected] -> [email protected] changelog #339

rvagg opened this issue Jan 13, 2015 · 11 comments

Comments

@rvagg
Copy link
Member

rvagg commented Jan 13, 2015

TC meeting today decided it would be good to have at least a broad-strokes changes document to show what's different in this release but we have to divide the work.

Need volunteers for each of the following sections (not limited to TC, anyone knowledgeable in the area can do it), please post a comment and say which module you're doing, then when you're done post a link to wherever you've prepared your document and I'll aggregate it into a single format. Please use Markdown:

  • assert
  • buffer & smalloc (I believe that's a logical grouping)
  • child_process
  • cluster
  • console
  • crypto
  • dgram
  • dns
  • domain
  • events
  • fs
  • http & https
  • module (module system in general)
  • net
  • os
  • path
  • process
  • querystring
  • repl
  • stream
  • sys
  • timers
  • tls
  • url
  • util
  • vm
  • zlib

also a section on major V8 changes would be good, that could be split up to:

  • language features
  • other V8 changes to expect

Writing should be concise and user-facing, not a bunch of commit log entries. What should people expect when they try this new beast out? What to look for, what they'll need to take into account when adapting their code, what new features to experiment with.

@rvagg
Copy link
Member Author

rvagg commented Jan 13, 2015

prematurely pressed submit somehow, updated description after initial issue creation ^

@rvagg
Copy link
Member Author

rvagg commented Jan 13, 2015

and to clarify timing: we need this for 1.0.0, so preferably within the next hour or two!

@badeend
Copy link

badeend commented Jan 13, 2015

There is already work being done at https://code.stypi.com/domenic/iojs-1.0-changelog.md

@domenic
Copy link
Contributor

domenic commented Jan 13, 2015

If someone could figure out a shell script or GitHub URL or something that does a rich (rendered) diff of the markdown docs from Node 0.10.35 to io.js 1.0.0, I think that would help immensely.

@domenic
Copy link
Contributor

domenic commented Jan 13, 2015

This script seems to do the trick:

#!/usr/bin/env bash

curl https://raw.githubusercontent.com/iojs/io.js/v1.x/doc/api/$1.markdown > $1.iojs.markdown
curl https://raw.githubusercontent.com/joyent/node/v0.10.35/doc/api/$1.markdown > $1.node.markdown
wdiff $1.node.markdown $1.iojs.markdown | sh ./markdown-format-wdiff.sh > $1.changes.markdown
greadme $1.changes.markdown

using https://raw.githubusercontent.com/netj/markdown-diff/master/markdown-format-wdiff for markdown-format-wdiff.sh

@domenic
Copy link
Contributor

domenic commented Jan 13, 2015

OK, I went through diffs of all the docs and filled in anything that was missing. The stypi is pretty up-to-date. I pasted a snapshot into https://gist.github.com/domenic/ed1bd3628748000acfe5 just in case someone accidentally deletes the whole thing.

I left a "still to-do" section at the top which contains the following:

  • Fill out TLS section
  • Fill out cluster section
  • Better explanation for HTTP keep-alive changes?
  • Fix links to docs once there are actual docs on the io.js web site. Probably add more links to docs.
  • Flesh out the "General" section a bit more maybe with some flavor text. "IO.js is the result of more than 2 years of work that never saw the light of day over on joyent/node, plus our own goodies, blah blah blah."
  • Maybe add discussion of changes in TLS support in the General section.

But otherwise I think we did what we could. Hope it helped! I'm going to go back to my day job now but let me know if there's anything else I can help with here.

@indutny
Copy link
Member

indutny commented Jan 13, 2015

@domenic filled the TLS/crypto holes in https://code.stypi.com/domenic/iojs-1.0-changelog.md

@rvagg
Copy link
Member Author

rvagg commented Jan 13, 2015

@bnoordhuis are you able to take cluster and maybe keep-alive, or is there someone else who feels more qualified to do keep-alive?

@bnoordhuis
Copy link
Member

I'm afraid I have to sign off in a few minutes. I have to get up early for a funeral tomorrow.

@domenic
Copy link
Contributor

domenic commented Jan 13, 2015

We could always leave those as "(This section of the changelog is still in-progress; check back later)"

rvagg added a commit to rvagg/io.js that referenced this issue Jan 14, 2015
Collaboratively edited by many people in
https://code.stypi.com/domenic/iojs-1.0-changelog.md
and includes a summary of changes in each major section of the
project from a user-facing perspective from Node.js v0.10.34
to io.js v1.0.0.

Renamed file to CHANGELOG.md from ChangeLog.md

Fixes: nodejs#339
rvagg added a commit that referenced this issue Jan 14, 2015
Conversion of the ChangeLog includes headings, compacted lists,
links for commits to GitHub (iojs/io.js) and links to issues on
GitHub (joyent/node)

Fixes: #339
Reviewed-By: Fedor Indutny <[email protected]>
rvagg added a commit that referenced this issue Jan 14, 2015
Collaboratively edited by many people in
https://code.stypi.com/domenic/iojs-1.0-changelog.md
and includes a summary of changes in each major section of the
project from a user-facing perspective from Node.js v0.10.34
to io.js v1.0.0.

Renamed file to CHANGELOG.md from ChangeLog.md

Fixes: #339
Reviewed-By: Fedor Indutny <[email protected]>
@rvagg
Copy link
Member Author

rvagg commented Jan 14, 2015

done, with excellent collaborative results via stypi.com thanks to @domenic

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

5 participants