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

Release Proposal: v2.4.0 #2189

Merged
merged 2 commits into from
Jul 17, 2015
Merged

Conversation

Fishrock123
Copy link
Contributor

The usual churn and stuffs. Semver-minor because the new --track-heap-objects flag.

@rvagg What you think, release tomorrow or friday?

@nodejs/collaborators I don't think it's been messaged properly, but anyone can propose a release for us too. :)

To get the formatted changelog:

$ npm i -g changelog-maker
$ changelog-maker --group
# optionally pipe the latter into your clipboard ala (changelog-maker --group | pbcopy) (OS X)

Additionally, if anyone is interested in doing releases, you don't need to be a TSC member. I did my first release before I was one!

@Fishrock123 Fishrock123 added the meta Issues and PRs related to the general management of the project. label Jul 16, 2015
@rvagg
Copy link
Member

rvagg commented Jul 16, 2015

sorry about the changelog-maker formatting bork there, being fixed here: nodejs/changelog-maker#19 /cc @maboiteaspam

@maboiteaspam
Copy link

Well noted, thanks. Few hours from now before i can free it from that bug.

@thefourtheye
Copy link
Contributor

I am fairly active these days and I would love to do the releases :-) Do we have specific timeline for releases?

@rvagg
Copy link
Member

rvagg commented Jul 16, 2015

Thanks for volunteering @thefourtheye. As we're investing a significant amount of trust on releasers I don't think we can be fully open about the process. While we're not limiting this to TSC members it should be (a) limited to collaborators and (b) limited to individuals who have earned a certain amount of trust, and that takes time. We need to give access to the server containing the binaries and we're giving out the ability to push code to users who trust us as a collective and we have to be careful with that trust placed in us. I might punt it over to @nodejs/build to see if we can come up with a clearer definition & process and get it ratified by the TSC.

We do have a need to expand the group of releasers though, exacerbated by needing at least two groups: one for general releases and one for LTS releases, perhaps with some overlap but they are slightly different roles. Thankfully we've started expanding on the 0.10/0.12 side too which connects directly to the needs of LTS.

@cjihrig
Copy link
Contributor

cjihrig commented Jul 16, 2015

I'm interested in getting involved with doing releases.

@thefourtheye
Copy link
Contributor

@rvagg No problem :-) I totally understand :-)

@thefourtheye
Copy link
Contributor

I am not sure why, but #2120 is missing. #2176 already has two LGTMs and it is tagged as semver-minor. So, if it can be landed, it can also set sail in 2.4.0 boat.

@Fishrock123
Copy link
Contributor Author

@rvagg / @maboiteaspam changelog-maker "forgot" 6 commits..

Above it only caught 11 while there are actually 17: 1a340a8...master
(Please be careful when changing tools people use, just like core!! :P)

@Fishrock123
Copy link
Contributor Author

@thefourtheye however, you can start by proposing a release sometime. :)

Notable changes

* src: Added a new `--track-heap-objects` flag to track heap object
allocations for heap snapshots (Bradley Meck)
nodejs#2135.
* readline: Fixed a freeze that affected the repl if the keypress event
handler threw (Alex Kocharin) nodejs#2107.
* npm: Upgraded to v2.13.0, release notes can be found in
https://github.com/npm/npm/releases/tag/v2.13.0 (Forrest L Norvell)
nodejs#2152.

PR-URL: nodejs#2189
@Fishrock123
Copy link
Contributor Author

@rmg
Copy link
Contributor

rmg commented Jul 17, 2015

grabs popcorn and watches the build console

@Fishrock123 Fishrock123 merged commit a764ac4 into nodejs:master Jul 17, 2015
@Fishrock123
Copy link
Contributor Author

All done, minus rpi1 (armv6) as usual.

@nodejs/evangelism please RT / promote https://twitter.com/Fishrock123/status/622193026253783040 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants