-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Comments
prematurely pressed submit somehow, updated description after initial issue creation ^ |
and to clarify timing: we need this for 1.0.0, so preferably within the next hour or two! |
There is already work being done at https://code.stypi.com/domenic/iojs-1.0-changelog.md |
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. |
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 |
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:
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. |
@domenic filled the TLS/crypto holes in https://code.stypi.com/domenic/iojs-1.0-changelog.md |
@bnoordhuis are you able to take cluster and maybe keep-alive, or is there someone else who feels more qualified to do keep-alive? |
I'm afraid I have to sign off in a few minutes. I have to get up early for a funeral tomorrow. |
We could always leave those as "(This section of the changelog is still in-progress; check back later)" |
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
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]>
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]>
done, with excellent collaborative results via stypi.com thanks to @domenic |
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:
also a section on major V8 changes would be good, that could be split up to:
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.
The text was updated successfully, but these errors were encountered: