Dylan Schiemann | 11 Apr 01:51 2014

Dojo 1.10 feature freeze date: May 7th

Based on the open issues and pull requests for 1.10 (
https://bugs.dojotoolkit.org/wiki/ProjectMeeting/2014-04-09 ), we have
decided to set a feature freeze date for Dojo 1.10 of May 7th.

Please take time to review and triage any bugs assigned to you, to help
review the open pull requests, etc. before then so we can have a solid
release shortly thereafter.


Dylan Schiemann
SitePen, Inc.
2014 Workshop schedule in the US, Canada, England and Switzerland:
SitePen Insider: http://sitepen.com/insider/

dojo-contributors mailing list

Colin Snover | 6 Mar 17:45 2014

Commit policy reminder


As part of the outcome of a discussion during the Dojo meeting
yesterday, I said I would send a reminder to all committers about the
process for adding code to the repository.

The policy that we have in place for committers is at
<https://github.com/dojo/docs/blob/master/developer/github.rst>. Please
take a moment to review the policy if you have not read it recently and
are planning on committing code in future.

Also, please make sure whenever possible that test cases are being
updated when adding fixes or enhancements.



Colin Snover
Mark Hays | 27 Feb 00:08 2014

Dojo 1.7 IE11 testing

Hi everyone, it is that time again:

To my knowledge, I backported all of the changes we made to 1.8 for IE11 support+making the test happy, but there are likely further changes in the 1.7->1.8 timeframe needed to make all of the tests pass. I'll keep looking at this, but any help at this point would be appreciated.

Also I found with the latest Java there is a control panel option to add sites as exemptions to the new security checks. If you add your test machine name to the exemption list, as well as turn off the usual certification checks etc, Java will not harass you about the robot anymore.

Failing tests
validationtextbox: euroformat and set constraints currency
combobox mouse: plaaceholder focus/blur
combobox a11y: wrap without more choices
ditto for filteringselect

place: off by one
menu_mouse::context menu mouse::close form widget
menu_a11y: click new using enter
Dialog: close 2nd dialog
validationtextbox: euroformat and set constraints currency
Select: hideDialog
combobox mouse: plaaceholder focus/blur
combobox a11y: wrap without more choices
ditto for filteringselect
ContentPane-remote: preload=false
AccordianContainer::animation::select pane 3
dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
Colin Snover | 21 Feb 17:06 2014

Dojo 1.9.3 and 1.8.6 released

Hi everyone,

I am pleased to report that Dojo 1.9.3 and Dojo 1.8.6 are now available
for download.

Dojo 1.9.3 is a standard maintenance and stability release, with the
special exception of the addition of a `useSourceMaps` option for build
profiles. In Dojo 1.9, source map support was added to the toolkit, but
with no way to disable generation of source maps. You may now set
`useSourceMaps: false` in your build profile in order to avoid
generating source map files.

Dojo 1.8.6 is a maintenance and stability release which adds support for
IE11. A lot of extra effort went into this release to ensure that all
test suite failures in all browsers were resolved. A special thank you
to Mark Hays, Brandon Payton, Ed Hager, Bryan Forbes, and Bill Keese for
their help in completing this work.

Download Dojo 1.9.3: http://dojotoolkit.org/download/
Download Dojo 1.8.6: http://downloads.dojotoolkit.org/release-1.8.6/

Fixes in 1.9.3:
Fixes in 1.8.6 and 1.9.3:

CDN releases are forthcoming.

Best regards,


Colin Snover
Dan Dumont/Westford/IBM | 19 Feb 19:27 2014

AUTO: Dan Dumont is out of the office 10/19/2009 (returning 02/24/2014)

I am out of the office until 02/24/2014.

Please contact Steve Mark if you need something right away.

Note: This is an automated response to your message  "Re:
[dojo-contributors] 1.8.6" sent on 2/18/2014 4:10:41 AM.

This is the only notification you will receive while this person is away.
Bryan Forbes | 14 Feb 00:03 2014


Are there any more backports that need to happen before 1.8.6 can be
released? If not, we should probably release it within the next week.


Bryan Forbes

GPG Fingerprint
3D7D B728 713A BB7B B8B1  5B61 3888 17E0 70CA 0F3D

dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
Karl Tiedt | 3 Feb 20:09 2014

Fwd: [GSoC Mentors Announce] Now Accepting Applications for Mentoring Organizations for GSoC 2014

It's that time again, I'm still on the mailing list with Google so on the off chance that nobody else sees this today, I am forwarding it on so hopefully someone can pick this up. I cannot devote enough time to put this together despite how badly I would love to do it. 

-Karl Tiedt

---------- Forwarded message ----------
From: Carol Smith <carols <at> google.com>
Date: Mon, Feb 3, 2014 at 1:01 PM
Subject: [GSoC Mentors Announce] Now Accepting Applications for Mentoring Organizations for GSoC 2014
To: GSoC Mentors Announce <gsoc-mentors-announce <at> googlegroups.com>

Hi all,

We're pleased to announce that applications for mentoring organizations for Google Summer of Code 2014 are now being accepted [1]. If you'd like to apply to be a mentoring organization you can do so now via Melange [2]. If you have questions about how to use Melange, please see our User's Guide [3]. Please note that the application process has changed a bit from previous years: to apply you must now create your individual profile and then an organization profile before submitting your application. 

Please note that the application period [4] closes on 14 February at 19:00 UTC [5]. We will not accept any late applications for any reason.

[1] - http://google-opensource.blogspot.com/2014/02/mentoring-organization-applications-now.html
[2] - http://www.google-melange.com
[3] - http://en.flossmanuals.net/melange/
[4] - http://www.google-melange.com/gsoc/events/google/gsoc2014
[5] - http://goo.gl/bYYgV3


You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors Announce List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gsoc-mentors-announce+unsubscribe <at> googlegroups.com.
Visit this group at http://groups.google.com/group/gsoc-mentors-announce.
For more options, visit https://groups.google.com/groups/opt_out.

dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
Patrick Ruzand | 3 Feb 14:27 2014

dojotoolkit nightly down ?


It seems the dojo nightly is down (using

Is it a temporary server issue or has it been put down for a particular reason ?


Bill Keese | 30 Jan 23:53 2014

where to put structural styles

Does anyone have any arguments for whether widgets' structural styles (ex: display:block, not colors and fonts) should be in CSS files vs. in the templates/set in javascript?

The cosmetic styles like colors should presumably be in CSS files, so that an app can override/replace them easily, but for styles that will theoretically never change, it's more debatable.

dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org
Christophe Jolif | 22 Jan 09:51 2014

IE11 backport

Hi all,

As I think I already mentioned, at least to Dylan, we will not only
have IE11 support to be backported to 1.8 but also 1.7... If there is
nobody handling this I guess Mark will start working on this. I
suspect that with a bit of luck and all the good work on 1.8 this
might end up being a bit simpler.

Speaking of 1.8 and according to his last mail 2 days ago Mark has
fixed the editor problems that were IE related and/or 1.8 specific so
it sounds like we should be good to push the changes and probably
release? Is there something specific blocking pushing the IE fixes
and/or releasing 1.8.6?


Ben Hockey | 13 Jan 18:39 2014

ownership of code

at the moment, i’m involved in 3 different pull requests (https://github.com/dojo/util/pull/7https://github.com/dojo/dojo/pull/49https://github.com/dojo/dojo/pull/47) that i’ve reviewed and in my opinion are either ready for commit or nearly ready to commit and i’m reluctant to commit them myself because i’m not clear if it’s my place to do so.  i want to be respectful of our process but i’m honestly not sure that this process is clear to me.

there is a point of view that could be taken where all committers are created equal and so anyone with access to commit code can commit to whatever they have access to.  an alternative point of view is that we have owners of various parts of the code and only those who “own" the code designate who may commit to those parts of the code.  during the time i’ve been involved with dojo, i think i’ve seen evidence of both of these points of view.

i see potential pitfalls with either point of view - with too many people committing and nobody clearly designated as the oversight for parts of the code, the quality is possibly going to degrade but with too few people allowed to commit, progress is limited by the capacity of the owner.

what is our (current) stance on this as a community of developers working together?  if our stance is that we have owners of the code then who owns what?  i just want to play by the rules :)


dojo-contributors mailing list
dojo-contributors <at> mail.dojotoolkit.org