I had asked Rawld about the veracity of a couple of notes in the release
notes a week or so ago but never got a response; specificallyhttp://livedocs.dojotoolkit.org/releasenotes/1.7#script
Anyone else have any ideas on whether these are true or not? At the
very least I could've sworn loading layers via script tags still worked,
though loading source modules may not. The 2nd section, about global
variables, just sounds completely off to me, but maybe it's due to the
way the examples are framed (inside plain script tags; maybe it's
supposed to be talking about modules?).
Also, we will have to update the reference guide link at the very top of
the release notes, to not point to livedocs.
Speaking of that blurb at the top, apologies for being blunt, but
calling the documentation "better than ever", at least in terms of the
wiki content, is somewhat laughable. Over the past few nights I have
been QA'ing articles regarding individual functions in Dojo core, and
even among those, I have found an alarming number of broken AMD-format
examples, mostly due to missing or wrong dependencies. On top of that,
others just don't follow the conventions we should be promoting. If we
expect people to be able to pick this up, the docs can't be wrong.
To that end, I'll continue doing what I can (I've been slowly working my
way down the dojo/index page - currently I'm midway through the
dojo/_base/html listing), just to make sure that existing examples
actually work, and improving wording/explanations where I deem necessary
and easily possible.
Some pages don't even have AMD-style examples (or even pages at all,
e.g. dojo.isDescendant and dojo.setSelectable which are listed on
dojo/_base/html), but I'm working under the prioritization that "wrong
docs are worse than no docs".
If anyone wants to help QA these things and wants to sync up, let me
know. (If you're an IRCer, hit me up on freenode as kgf, it'll probably
be easier to coordinate there.)
That said, I can't possibly expect this to be fully QA'd in any
"reasonable" amount of time if we want to "ship" soon. For that reason,
I would *strongly* urge that we do *something* to enable us to push
further fixes to reference-guide after the initial 1.7 push. This
hasn't been possible in the past because the wiki is "trunk" and there
is no "branching" of it, and thus once revisions specific to 1.8 start
coming in, it's too late.
I think Pete wants to look into getting rstwiki working locally again
this weekend, but I don't know how soon that can be put live; if it's
possible to kick that into gear sometime during 1.7's lifetime, allowing
us to fix doc issues as people find them rather than have them frozen in
time until 1.8, that would be great. We already had enough people
complain about the same handful of broken examples in the 1.6
reference-guide doc push over the last half year; it's likely to be even
more painful this time around.
Sorry for rambling so long. tl;dr - I'm working on ref-guide doc QA
when I can, and there's no way it'll be fit to ship too soon but I
presume that won't stop anyone (just like it didn't 2 weeks ago).
On 11/11/2011 5:03 PM, Bill Keese wrote:
Looks like a good list. I'm not sure if the release notes need to be
updated for CDN or not. Guess we'll find out after Pete pushes to google.
On Sat, Nov 12, 2011 at 6:07 AM, Adam L. Peller <adam at peller.org
I attempted to make one at the top of this thread. I'll update it.
release notes: ready to go (any takers for review?)
ref-guide needs to be pushed with necessary infrastructure work,
codeglass, more? (Pete)
cdn: ready at http://archive.dojotoolkit.org/cdn/
to send to Google
api docs: publish 1.7 xml (Tom, done)
update website (Torrey)
announce on dojo-interest, other PR (Pete, Dylan, others?)
On Fri, Nov 11, 2011 at 4:01 PM, Dylan Schiemann
<dylan at dojotoolkit.org wrote:
Ok, we've had 1.7 near ready for quite some time, and we're struggling
to get it out the door.
It's been a tremendous about of work, but it's time to get the last
details in place and announce it.
Where's the todo list, status, and plan? I suggest we get a clear todo
list everyone can follow, we get this done, and get it live.
Please respond with what you know as far as what must get done, who's
working on it, what's blocking, and how to help.
dojo-contributors mailing list
dojo-contributors at mail.dojotoolkit.org
<mailto:dojo-contributors at mail.dojotoolkit.org>http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
dojo-contributors mailing list
dojo-contributors at mail.dojotoolkit.orghttp://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors