1.2 release

[sindresorhus]

We should do another release now that we've converted most of the apps to Bower and have an awesome new sidebar.

• Write a G+ post about the release and how we use Bower and some other smart stuff.
• Merge PRs
• Any open issues we should fix before release?
• Before release, go through the apps and site and make sure everything works correctly.
• Update site url on download link, changelog, and tag release.
• Announce on Twitter/G+ (RT/RP!)
• Send in to JavaScript Weekly, Hacker News and Reddit.

Feel free to add anything else. We can reuse this one for other releases.

We're shooting for a release on thursday, but we should already begin preparing.

@sindresorhus @addyosmani @passy @stephenplusplus

[passy]

We should do another release now that we've converted most of the apps to Bower.

... and have the awesome new sidebar. :)

[heavensrevenge]

Well what about a way to split the view vertically or with an adjustable separation to see the source to multiple sources in the same tab?
A side-by-side comparison by you instead of having to go so deep into each implementation to compare the differences more easily would be nice. Beyond manually comparing the implementations by using multiple tabs or comparing the sources in our editors.

[passy]

@heavensrevenge There's an ongoing discussion about a code comparison tool. We would love to hear your opinion there: tastejs/meta#3

[addyosmani]

I'd like to wait on the React and Polymer apps to be added before doing a release. Would you guys be down for us rolling out a release Wednesday?

Should give us time to work through many of the issues on the list above.

[sindresorhus]

Sure

[passy]

+1

[passy]

Pull request / issue sprint sometime next week?

[sindresorhus]

Hah, this slipped again...

Yes.

[stephenplusplus]

Rough Draft of checkbox 1...

Let me know if I went in a weird direction :D

---

TodoMVC To-Did All That?!

Addy Osmani's TodoMVC project, now under the umbrella of TasteJS, just stamped out a new release. With this iteration come some exciting changes.

In an effort to keep up with the ever-changing landscape of web development, TodoMVC has incorporated Bower into each of its example applications. To the interested developer, that means all you have to do is clone the repository, navigate in your terminal to the demonstration you're interested in, then run bower install to pull down all of the relevant source files.

TodoMVC has a new approach to solving the intricate challenge of making the "latest and greatest" approachable for a newcomer. After all, that's what the project is all about. With the new release, you'll see something new on each framework's application. The "Info Bar" collects several educational resources from the community around each framework, allowing you to use TodoMVC as a starting point in your efforts to learn a new tool.

Several example applications have been upgraded to the latest framework release (some even by the authors themselves). Some new frameworks have been welcomed to the project as well:

• Polymer
• Vanilla JS - (completely re-written)
• Flight
• React
• and more!

Behind the scenes, working alongside Addy Osmani and Sindre Sorhus, two new team members have been welcomed to the project. Be sure to give Pascal Hartig (@passy) and Stephen Sawchuk (@stephenplusplus) a high five next time you see them. Their hard work has crushed several bugs, tweaked important specification requirements, and unified the code style shared between demonstrations.

If you haven't already, TodoMVC is definitely worth checking out for a true, unbiased presentation of several frameworks-- over 50!

[addyosmani]

^ I love it. Nice work, sir! 🍰

[passy]

Fantastic as always, Stephen. Can't wait for all the ✋!

[sindresorhus]

This is really good.

One thought. TasteJS is mentioned, but we have yet to announce what TasteJS is all about. Should we do that first, do it in this blog post or wait until later?

[addyosmani]

I think we should put together a short mission statement on the TasteJS site and we can then consider it announced. Mostly because we already told people about TasteApp. I'd rather announce TasteJS more formally when we have something to show (e.g a first implementation). How does that sound?

[passy]

Sgtm!
On Jun 29, 2013 1:21 PM, "Addy Osmani" [email protected] wrote:

I think we should put together a short mission statement on the TasteJS
site and we can then consider it announced. Mostly because we already told
people about TasteApp. I'd rather announce TasteJS more formally when we
have something to show (e.g a first implementation). How does that sound?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/597#issuecomment-20228293
.

[sindresorhus]

Sure

[addyosmani]

React app has been made spec-compliant (we probably want to make a call on whether or not to go red on it) and we now have a Firebase app! (woo!)

To keep things visual, I wouldn't mind us throwing in a single row graphic/s with the icons for the major projects that now have implementations for the blog post.

We can definitely use what @stephenplusplus put together as a base 👶

[addyosmani]

Filed a PR to update the Polymer app while we're at it. As mentioned on IM, I think we should target getting the release out this week. I propose Tuesday or Wednesday if JSW/newsletters are something we want to be mentioned in.

Can we actively try to resolve outstanding issues we would like to see land before 1.2 soon?