Branding Release Channels

[mikeal]

We have a number of builds that we want to be consumed by different audiences and we need to find a way to message those channels and a strategy for promoting them to the correct audience.

This topic is descendent from the big release process issue: #1997

• Lastest LTS
• Supported LTS
• Maintenance Mode LTS (Is this the right term?)
• Incubating Master (we need to start incubating master releases before promoting for wider consumption)
• Incubated Master (Previously referred to as "stable" or "current" master, basically the latest master build that passed incubation)
• Latest next release.

Obviously we won't feature all of these on the front page and we may have different strategies for promoting them on twitter, that's one of the things we need to figure out along with the branding.

Pinging relevant working groups:
@nodejs/website
@nodejs/evangelism
I'll also make sure the Marketing Committee at the foundation lends their expertise.

[Fishrock123]

@mikeal did we figure this out ever?

As far as I know things now sit like this:

• next / dev (master)
• stable
• LTS
• maintenance

Maybe we should still discuss what master releases should be called?

[mikeal]

Nope! Let's put this on the back burner until the new website is up. Right
now let's just refer to releases by their number. Once we have a bunch of
these live my suggestion would be to reach out to the foundation's
marketing committee to get their input as branding isn't our core
competency :)

On Tue, Aug 25, 2015 at 9:39 AM, Jeremiah Senkpiel <notifications@github.com

wrote:

@mikeal https://github.com/mikeal did we figure this out ever?

As far as I know things now sit like this:

• next / dev (master)
• stable
• LTS
• maintenance

Maybe we should still discuss what master releases should be called?

—
Reply to this email directly or view it on GitHub
#2216 (comment).

[Fishrock123]

Moving to nodejs/nodejs.org#200