> To get back to what I took as FND's original point, the issue here is > not this one bug about jQuery, but rather how long it is taking it, > as an example of many bugs, to get resolved. A healthy open source > project "should move more rapidly and be more responsive".
That was indeed my main point - the jQuery lag is just a symptom. > The intent is to fix ticket 472 and upgrade to the latest version of > jQuery in the next TiddlyWiki release. Further to the above, I currently have no idea when that release is gonna be - I don't think anybody (including the core maintainer) does. Extrapolating from past and current trends, I'm concerned that's gonna be months rather than weeks. > The move to github is an effort to shake things up, blow out the > dust a bit, but it will not make enough of a difference if there is > not a fundamental change in the attentiveness, accessibility and > responsiveness of the people responsible for the core. +1 (Note that my intention here is not to spread pessimism, but rather to constructively highlight significant issues.) -- F. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
