0.3 Release

[addyosmani]

I think we should try to get a 0.3 release finalised for the end of this week. Since 0.2 we've had a number of significant changes to the project including cleanups, tweaks, the boilerplate, a todo specification and new apps such as the Dojo example.

I really wanted to get #59 sorted out too, but I'm not sure we'll have time. I might try getting this finished myself during the week.

Some tasks related to a release are:

• Update https://github.com/addyosmani/addyosmani.github.com/tree/master/todomvc to reflect the new apps. Also revise the page language a little to better match the project README (e.g moving towards referring to apps as using the MV* pattern over MVC as this is more accurate)
• Tag the release on Friday (and update any download links above)

Other than these items is there anything else you think we should be covering for 0.3? (this will be the last major release before the application rewrites for 1.0)

//cc @boushley @sindresorhus

[addyosmani]

Side-note: I've been thinking a little more about the future of the project and how else it might assist developers in selecting a framework of choice. Obviously one thing we're missing right now are examples that are hooked up to a technical stack (so people can see how things work from end to end).

My initial efforts on this for Backbone.js can be seen here: https://github.com/addyosmani/backbone-boilerplates, where Todo applications are connected up to stacks such as Node/Mongo and Sinatra/Mongo. I'm wondering if it would be useful to include this in 0.3 as a teaser of things to come, but I don't want us to be doing anything premature that smells of feature-creep.

What do you guys think?

[boushley]

I think that going for 0.3 this weekend would be a good move. I don't see much of anything that we need to do for 0.3 other than the ones that you listed.

As far as including the "teaser" of the future work, I don't see any problems with that as long as it is labeled as such. I'm not sure how much of that we will want to bundle into the next release though. We already have a fair amount of work with the rewrites of the current applications, and the redesign. So they may be "teasers" past the next release as well.

I haven't gotten much work in lately as I've been preparing for a job change. The one down side with my new position is that the non-compete/NDA is pretty strict, meaning that I'll have to get specific approval for any out of work projects (including open source like this) so we'll see how that goes.

[addyosmani]

@boushley Completely understandable. Whatever time you are able to contribute is still much appreciated :)

[sindresorhus]

I think having a full stack example is a very good idea, though I don't see the point of adding it in 0.3. We should rather just get 0.3 out the door, and focus on 1.0, which should indeed contain a backend example.

Any reason the TodoMVC site is in the addyosmani.github.com repo instead of in a gh-pages branch in this repo?

[addyosmani]

@sindresorhus Mainly legacy. I don't mind moving it to a gh-pages branch on this repo at all.

With respect to the backend examples, I think a nice compromise would be: lets not include it for 0.3, but just have a link to the experimental repo so people are aware we're thinking of it for the next major release.

[sindresorhus]

Yes, please do :)
We could either have the framework folder as a submodule in gh-pages or mirror the master branch into gh-pages (master would contain the site), then the site would always be up to date.

[addyosmani]

@sindresorhus I think if we can move ahead with a submodule that would be great. We can opt for the mirror if we run into any complications with that.

[addyosmani]

@sindresorhus re: earlier, I've removed the todomvc site folder from the other repo. Could you let me know if there's anything else you need?

[sindresorhus]

That should have done it, but it's still stuck on the old site, even though I pushed some changes to gh-pages afterwards. Hmm. Can you check the admin that gh-pages is enabled?

[addyosmani]

Hmm. It's definitely enabled. I wonder if its a caching issue?

[sindresorhus]

Apperently the reason the new site didn't show is that submodules use another format than the one I'm used to, so it didn't work. Fixed now.

git@github.com:addyosmani/todomvc.git -> git://github.com/addyosmani/todomvc.git

It's live here.

[addyosmani]

@sindresorhus Dude - I love what you did with this: http://addyosmani.github.com/todomvc/. Nice work :)

I think we'll add a team section in the footer a little like http://www.modernizr.com when we have more time.

[sindresorhus]

😃

Just pushed a commit to make the site fully responsive. Try resizing the browser window ;)

[addyosmani]

@sindresorhus you are the man, sir ; ) Site is looking great! I think this will definitely hold us up for a while.

Tomorrow I'm going to run through some final testing of the current version of the project we have in master then push 0.3 live. The changelog should be fun to look at :p

[boushley]

I agree with @addyosmani this looks fantastic @sindresorhus Great job!

[addyosmani]

@sindresorhus I've just merged and added references to the new Closure example that we got a PR for today. I've reviewed the code and cross-browser tested so should be okay.

Before tagging, I noticed that the current introduction/index in master is using the older version of the template. Do you think we should update that to the newer one? (all needed is copying what we have in gh-pages and adding the reference).

The other differences are that the newer template for the homepage doesn't include a) links to frameworks (it does demos) and b) links to contribs. I think this is absolutely fine for the main site, but wonder if we should continue including them in the version for download.

If you think you might be able to look at this today, feel free to let me know, otherwise I'll tag sometime this afternoon :)

Thanks!

[sindresorhus]

@addyosmani I've noticed the "introduction" folder. That's why I asked if we should have the site on master and just mirror it to gh-pages, so we didn't have to duplicate. Is it neccecary to have the "introduction" folder in the master? It's on the site anyway.

Know about the missing links to framework and contributors, just been thinking about the best way to present it.

Instead of having a manual list of contributor, we can instead maybe link to the contributors list on GitHub, or we can even fetch it using the API?

Instead of having 2 identical lists of frameworks, one for demos and for direct links, we can use a Bootstrap popover to show a short description of the framework and a link to it when you hover over it?

Will work on this when we have an agreement on it ;)

[addyosmani]

@sindresorhus I'd like us to have the introduction folder be in master (although I don't personally mind if it's mirrored from gh-pages or the other way around). Whatever you feel is best there :) I would like to ensure that if people want to browse locally once they've downloaded the tagged releases they're able to easily do that from a single page.

I don't mind us opting for the GH contrib list. The only issue I can see there is that for about 3 of the applications, we pulled in the earlier versions from other repos and the authors on those wouldn't appear on that list. We might be okay with that for now because contribs are listed on each todo app.

As for the popover idea..love that. Happy for us to try that out! :)

[sindresorhus]

@addyosmani We could continue to use submodules, but that would mean submodules both ways, which seems kinda dirty. I think we'll go for everything in master, with a gh-pages mirror, that's simple. The reason I suggested it is because right now, we have almost the same content in the README, the site, and the introduction folder, and I hate duplication ;)

I could just add them when I fetch the contributors list from the API.

Cool, will add it.

[addyosmani]

I think we'll go for everything in master, with a gh-pages mirror, that's simple

Let's go for it :)

[sindresorhus]

gh-pages is now a duplicate of master. To automatically update gh-pages when you push to master, do this:
http://stackoverflow.com/questions/1705224/github-how-to-include-files-from-master-in-new-git-branch-gh-pages

[addyosmani]

@sindresorhus Awesome!. (silly question, but does master now include the latest version of the site/re-themed one?)

[sindresorhus]

Yes, it does. The site should be developed on master, and it's automatically mirroed to gh-pages on push when you add the config in the last comment.

[addyosmani]

This is perfect. Thanks @sindresorhus!

[addyosmani]

How does this look? http://addyosmani.github.com/todomvc/ updated for 0.3 with details of what was updated, some changes to notices etc.

[sindresorhus]

Looks good. Think we can tag it ;)

[addyosmani]

@sindresorhus awesome. Tagging now :)

[addyosmani]

@sindresorhus You did a really great job on those tooltips. Just noticed them now :)

As 0.3 is out the door and pending confirmation of the Dojo fix it looks like it was released without any other problems, I'm going to say this was a success and close this issue. Thanks all!