LTS Meeting 2015-10-05 about lts HOT 7 CLOSED

Items from nodejs/node#3000 that should be resolved in this WG but can be informed by discussion there:

• We need a codename for the release, there is some discussion here with the current plan for the LTS WG to come up with a shortlist and then give the collaborators the chance to vote on their preferred option. It's looking likely that we'll be picking something off the periodic table. (Please don't bikeshed this topic in this issue, take it to #26 if you feel it's that important).
• Do we bake something into the LTS binaries to signify that they are LTS? I can't recall where this discussion was but we had talked briefly about possibly putting something in process.release, maybe process.release.lts: '201510' or process.release.lts: 'codename'. If we do this, then do we ensure we cut an actual release in the "first week of October" just to make sure we have this done?

from lts.

Yes I can take this on.
On Sep 29, 2015 4:14 AM, "Rod Vagg" [email protected] wrote:

@nodejs/lts https://github.com/orgs/nodejs/teams/lts I'm really sorry
that I messed up the meeting this week, it should have been today
(yesterday) but I completely forgot after a computer-free weekend and a
zone-out of all things Node. It's vital that we have a meeting next week
because we have to ship v4 LTS only days afterward! A meeting this week
would have been ideal. On that note, I'd like to ask if someone else would
mind taking over meeting planning and organisation for this WG? The timing
is really poor for me and I need to hand off some of my existing workload
anyway. Perhaps @jasnell https://github.com/jasnell?

Time: 8PM Monday October 5th UTC (1pm Pacific), or in your local timezone:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js%20Foundation%20LTS%20Meeting%202015-10-05&iso=20151005T20 PLEASE
NOTE DAYLIGHT SAVING SHIFT FOR SOME TIMEZONES

Agenda and minutes can be collected in here and copied into this repo
later:
https://docs.google.com/document/d/1DOcI2B8F0nuoz2hf6uidCrAG0N067YEAR192ljguJhc
(if you're attending the meeting and don't have write access to this doc
please give me your google login email).

Previous minutes:
https://docs.google.com/document/d/10RKDaijNGt2thmAcTHCRUzNOz9NcZNBbdklyzHXH9yo

Hangout on air for active participants:
https://plus.google.com/hangouts/_/hoaevent/AP36tYe1gWyx4ZbW2Uyl4oVBMn2ZgRw_viokqpxw5gjFHwnkJr9rfw

YouTube feed for observers and saved recording:
http://www.youtube.com/watch?v=wfg2nHXAQqI

Current invited participants, this list is not exclusive if you think you
should also join:

• @bnoordhuis https://github.com/bnoordhuis
• @dshaw https://github.com/dshaw
• @Fishrock123 https://github.com/Fishrock123
• @jasnell https://github.com/jasnell
• @misterdjules https://github.com/misterdjules
• @rvagg https://github.com/rvagg
• @shigeki https://github.com/shigeki
• @trevnorris https://github.com/trevnorris
• @geek https://github.com/geek
• @mhdawson https://github.com/mhdawson
• @ofrobots https://github.com/ofrobots
• @joaocgreis https://github.com/joaocgreis
• @srl295 https://github.com/srl295
• @zkat https://github.com/zkat

Agenda discussion can happen in this thread.

—
Reply to this email directly or view it on GitHub
#43.

from lts.

Sorry, will be on a plane during this meeting.

from lts.

Added nodejs/node#3035 to the agenda. This issue will need to be fixed at some point in a v4.x LTS release.

from lts.

ftr nodejs/node#3035 seems perfectly reasonable to land in LTS as it's really a bugfix and that's in scope for LTS, that's my personal assessment anyway. I'll be interested to see which resolution you choose but it seems to be something for the postmortem group to decide and guide in to core.

from lts.

Agenda item arising out of TSC meeting today: how to maintain V8 in LTS over the long-term

from lts.

group, please sanity-check nodejs/node#3212 for me to make sure I'm representing the decisions correctly on codenames

from lts.