Release bonanza! Dojo 1.4.4, 1.7.3, 1.8.0b1 released

Hi everyone! I’m pleased to offer not one, not two, but THREE new Dojo releases for your consumption.

Dojo 1.4.4 is now available. This is a maintenance release that backports browser fixes to add support for Internet Explorer 9 and Firefox 4+. Information on which fixes were backported to Dojo 1.4.4 is available on the bug tracker. This is basically identical to the Dojo 1.5.2 release that happened…whenever that happened! A little while ago. Thanks to kgf for managing this release.

Dojo 1.7.3 is now available. This is a bugfix release that resolves several issues with the 1.7 branch of Dojo, including issues with the i18n subsystem, legacy modules, and the build system running on Node.js. It also fixes a significant performance regression from 1.6 when loading many legacy modules and includes bugfixes for several other components. The full list of fixes for Dojo 1.7.3 is available also on the bug tracker.

Finally, Dojo 1.8.0b1 is now available. This is the first beta of the new Dojo 1.8 release and includes several exciting new features. A blog post written by interim supreme overlord Dylan Schiemann provides an overview of many of the most significant new features and enhancements coming to Dojo 1.8. There are close to 700 new features, enhancements, and bug fixes in this release, including a brand new documentation parser (written by yours truly) that will make the API browser work correctly again. As usual, the running list of changes that have made it into Dojo 1.8 so far is at the bug tracker.

Dojo 1.8 is on track at this point for a release in mid-to-late July. Beta 2, if necessary, will be released in about three weeks. CDN releases for Dojo 1.4.4, Dojo 1.5.2, and Dojo 1.7.3 have been submitted to Google. I will post again once those are made available.

OK, that’s it from me! Have a great solstice weekend.

Dojo 1.8 release schedule

In preparation for the release of Dojo 1.8, trunk is now in feature freeze, which means this code is considered feature complete for Dojo 1.8. This is the last step before a beta release. The release schedule is currently as follows:

Now: feature freeze
June 22: beta 1
July 13: release candidate 1 (note: if additional beta releases are necessary, each release will push this out by 1 week)
July 20: Final release (note: if additional rc releases are necessary, each release will push this out by 1 week)

Thank you to everyone that has helped make this release a success!

Dojo 1.4.4rc1 Released

The first release candidate for Dojo 1.4.4 is now available for download.  The focus of this release is to backport IE9 and Firefox 4+ compatibility fixes, as seen in 1.6.1 and 1.5.2, to the 1.4 line.

Download: http://download.dojotoolkit.org/release-1.4.4rc1/
Backport ticket: http://bugs.dojotoolkit.org/ticket/15508

If you’re interested in testing this release, please do so and report any regressions promptly; the final release of 1.4.4 is planned for next Friday, June 22.  Thank you!

CometD 2.5 Beta 1 Adds AMD Support

The CometD project just announced their first 2.5 beta, which adds AMD support to their Dojo-based JavaScript client, as well as their jQuery client with an AMD loader.

The release notes contain full details. They have set things up such that it will work with AMD syntax, and still work with the legacy dojo.require/dojo.provide syntax.

If you are using the require/provide syntax, you need to register a module path prior to requiring dojox.cometd:

dojo.registerModulePath("org", "../org");
dojo.require("dojox.cometd");

For AMD applications, either use the “tlmSiblingsOfDojo: true” configuration attribute, or use a configuration object specifying the “packages” field and map that to the location of cometd.

CometD 2.5.x ships updated demos that you can use as examples:

* Dojo 1.7 AMD-style demo: the Reload demo, the Chat demo
* Dojo 1.7 non-AMD demo: the Echo demo, the TimeSync demo

Please report any bugs you find to the CometD issue tracking system.

For Dojo 1.8, we will remove dojox/cometd from the repo, and add an svn:externals to the CometD project source code.

Dojo Recognized at the Great Indian Developer Summit

The Dojo Toolkit was recently selected as the 2012 recipient of an award for excellence in web development technology at the Great Indian Developer Summit. We are honored to receive this award. The conference has over 14,000 attendees, India’s largest tech event. Anuj Dubey and Lakshmi Sharma accepted the award on behalf of the Dojo Foundation.

The selection criteria for the award emphasized functionality, usability, innovation excellence, bleeding-edge features, and feedback from the developer ecosystem. The web development category specifically emphasized web development and deployment tools that are helping developers and designers push the boundaries of the web, which is consistent with one of Dojo’s primary objectives!

Dojo 1.7.2 status

Hi everyone,

Just a quick status update on 1.7.2. There were a couple of last minute build issues that were discovered in the RC which means that the release has been pushed back slightly. We’re hoping to have it out by Friday at the absolute latest; it may be out earlier than that depending upon how quickly the remaining issues can be ironed out.

Dojo 1.7.2rc1 released

Hello world,

I’m happy to announce the first release candidate for Dojo 1.7.2. This is a stability and bugfix release, and is the first to include official support for the newly released Firefox 10 ESR.

Download: http://download.dojotoolkit.org/release-1.7.2rc1/
List of fixes: http://bugs.dojotoolkit.org/query?group=status&milestone=1.7.2

Final release of 1.7.2 is planned for next Wednesday, so test and report any issues promptly! Thanks!

What’s coming in Dojo 1.8

Hi everyone,

I’m Colin, one of the release managers for Dojo 1.8. Today I wanted to talk publicly about the planned roadmap and our focus for the next major release of Dojo.

Near the end of January, a group of team members held a meeting to discuss our direction for 1.8. The discussion was a little larger than simply the 1.8 release and cut across a few different areas, but we did establish a reasonable release roadmap full of new features and enhancements. For the most part, Dojo 1.8 will have a much more tightly controlled scope than 1.7, and we’ll be keeping release blocking issues reserved for Dojo and Dijit packages (instead of DojoX packages) in order to ensure a more reasonable/sprightly release cycle than the previous two.

Briefly, the list of planned improvements for 1.8 are:

  • New standalone Router component
  • New I/O component (to replace the existing XHR module)
  • New calendar UI component
  • New documentation parser
  • Touch & HTML5 support for Dojo DnD
  • Unified Touch API for Dijit, Dojo Mobile, and graphical modules
  • More mobile widgets and general mobile support improvements, including the start of convergence between Dojo Mobile and Wink Toolkit
  • Better SVG and Canvas support in dojox.gfx
  • Improvements to dojox.app lifecycle management
  • Improvements to data binding in dojox.mvc
  • More application demos
  • More has-bracketing for feature detection and smaller builds
  • Bug fixes for CLDR generation, AMD conversions, and more

In addition to code improvements, some very important additional changes are being made during the 1.8 release cycle:

1. Documentation

Everyone agrees: where to find correct and accurate documentation remains confusing to end-users and we need to work on improving this. From a tooling perspective, it was decided that the best route forward here is going to be to focus on getting a new JS-based documentation parser up and running as soon as possible, both so it can be used to generate the correct documentation for the API browser, and also so that it can be used to provide reports about what areas of code are missing documentation. Rawld Gill and Colin Snover will be the primary people working on this piece, but as they are both busy, anyone interested in the fun and exciting world of parsing should volunteer to help (even if it is simply running code against it until it breaks and lodging bug reports in the issue tracker on GitHub). Longer-term, the plan is to try to combine API & ref guide as much as possible to provide a *single* point of authoritative documentation for any given component.

In addition to tooling, we are working on improving user feedback during this cycle in order to try to learn where we need to focus our documentation improvements the most. Links have already been added to the bottoms of the API browser, tutorials, and reference guide pages so users can submit feedback about pages that are not giving them the information they need. We encourage everyone to use these links to provide documentation feedback.

Finally, Dylan Schiemann will be helping to set up some targeted documentation sprints to improve the quality and availability of documentation. More on this at a later date.

2. Browser compatibility

There are some new components slated for development during the 1.8 cycle that are dropping support for old browser versions (IE6 and Firefox 3.6). These components are likely to be the first to be referenced from external repositories as part of the move toward independent repositories for DojoX projects. Since we are still committed to continuing support for a wide range of browsers and browser versions within officially supported code, we will be implementing browser support grading in 1.8 (a la YUI and others) to make it clearer to end-users what kind of support they can expect for a given platform (and to enable us to more gradually phase out support for these legacy browsers).

We also understand that users don’t want to be stuck on a toolkit upgrade treadmill, but still need their products to be able to support new browsers as they are released. As such, we are currently evaluating a proposal to perform quarterly backports of browser support fixes from trunk to Dojo 1.5 and newer to assure end-users that their products will be able to support newer browser releases for a reasonable period of time. The release of Dojo 1.5.2 was a trial step in this direction.

3. Bug tracker

Our bug tracker has not been meeting our needs effectively when it comes to managing releases and issues. As such, new plugins have been introduced to improve this tool. We are also planning on going through and aggressively reducing the number of open tickets in order to provide a more realistic and manageable look at what work needs to be done for 1.8 and beyond.


As mentioned in the roadmap, our planned feature freeze date is April 16, with final release hopefully occurring sometime in early June. Keep your eyes here for updates and some sneak peeks at what’s coming up in the new release!