[09:00:30] timmywil rwaldron gnarf mikesherov orkel m_gol jaubourg gibson042: meetin' time! [09:00:39] OH YEAH! [09:00:55] oh man, now i have to live up to it [09:00:57] boosh [09:01:17] i maded you guys an ajenda: https://docs.google.com/document/d/1MrLFvoxW7GMlH9KK-bwypn77cC98jUnz7sMW1rg_TP4/edit [09:01:20] hey [09:01:59] so it seems like 2.0 got a pretty warm welcome [09:02:11] at least no pitchforks [09:02:22] ;) [09:02:44] i put some tix in the agenda for 2.0.1, i think gibson042 has already done a couple of them [09:03:01] too bad we didn't get to deprecating this context stuff before 2.0 [09:03:05] but, well, it happens [09:03:13] yeah [09:03:26] hey, looking at these tickets, I'd like to bring up that it would be great if the changeset link that our hook inserts was actually a link [09:03:27] there are always a few things we find at the last minute [09:03:34] timmywil yeah [09:03:45] it would be great if the bug tracker worked most of the time [09:04:02] i still have an item to turn bugs.jquery.com into a "where do i go page" [09:04:04] I think it's just a matter of setting the href correctly in our commit hook [09:04:04] yes, Y U NO etc. etc. [09:04:05] gibson042: (屮'Д')屮 [09:04:16] rather than a "let me file a bug against core incorrectly" page [09:04:46] timmywil i thought it was on the trac side but could be wrong [09:04:56] ah could be [09:05:01] question: was it ever correct? [09:05:07] I don't think so [09:05:10] might have been when we were on svn [09:05:20] the "get off my lawn days" [09:05:32] oh man, it has to be long time ago... [09:05:38] 2008 or so [09:06:22] so on that YUI and closure thing, should we just shorten it to bool rather than argue they're doin it rong? [09:06:48] I don't care about yuglify if it's EOL but Closure might be important [09:07:08] we probably should do both, i.e. rename and ping sb from Google about the Closure issue [09:07:52] i dunno if anyone is using them and targeting ES3 envs where "boolean" is reserved [09:08:00] i dunno if those even exist! [09:08:28] Closure needs the --screw-ie8 option ;) [09:08:32] lol [09:08:34] yeah [09:08:56] i'd vote for just going with "bool" and being done with it [09:09:12] +1, though I'd ping Google guys, too [09:09:45] yeah, chad killingsworth is still working on Closure AO so i can mention to him as well [09:10:10] DaveMethvin, I don't seem to have access to this Google Doc [09:10:31] i think it's public, lemme check [09:10:50] yeah public https://docs.google.com/document/d/1MrLFvoxW7GMlH9KK-bwypn77cC98jUnz7sMW1rg_TP4/edit?usp=sharing [09:11:16] i'm getting an error from google docs sometimes [09:11:22] beeen kinda flakey this morning [09:11:34] I meant edit access but nvm ;) [09:11:43] we can't remove context in 2.1/1.11 [09:11:51] since it's not deprecated yet [09:12:21] yeah, but it gives us something to look forward to :) [09:12:31] it will be as of 1.10, though... is *that* enough notice? [09:12:50] for 1.11/2.1? definitely [09:13:18] hm, so we're not trying to keep complete parity between 1.10/2.0? [09:13:41] $.isPlainObject, now $.fn.context [09:13:48] deprecation is outside the code [09:13:54] it doesn't break parity [09:14:13] true :) [09:14:14] ok [09:14:36] how will it look on api.jquery.com? [09:14:41] and some diffs are okay, it depends on the specific behavior [09:14:57] as deprecated as soon as we ship 1.10? [09:14:57] here [09:15:11] yeah i will have it in a blog post [09:15:15] hey gnarf [09:15:54] actually kinda afk, but will read [09:15:59] so did we get agreement on changing bool to boolean? gibson042 timmywil ? [09:16:08] works for me [09:16:09] whoops boolean to bool [09:16:13] :) [09:16:17] that too :) [09:16:17] yep, +1 from me [09:16:40] okay [09:17:35] tracking the parallel versions is kind of tricky [09:17:53] so keep your eyes open on issues that need to be in two different versions [09:17:58] any idea on a better way? [09:18:07] two tickets seems extreme [09:18:29] we have 1.10/2.0 milestones etc. [09:18:32] I like the joint milestone approach [09:18:35] yeah [09:18:45] so this would be 1.10/2.0.1? [09:18:48] it'll be fine for most, some bugs might need 1.10 or 2.0 only [09:18:50] yeah [09:18:57] ok worksforme [09:19:11] such fun to make changelogs lately [09:19:15] ;) [09:20:00] so the 1.10 schedule [09:20:08] any particular feelings one way or the other? [09:20:27] beta before 2.0.1 might be OK [09:20:46] though betas are not widely used anyway so I'm not sure if it matters [09:20:51] i was thinking originally it would be nice to have 1.10 in June but if we want to keep a 1.x/2.x in sync it's kind of nice to have the two released relatively close to each other [09:21:15] yeah, we had some problems with keeping 1.9 & 2.0 in sync [09:21:19] i think we're in pretty good shape for 1.10 right now, once the 2.0 fixes are picked into it [09:21:24] I'd say the sooner the better; we ought to have corresponding 1.x and 2.x releases to come as concurrently as possible [09:21:25] so better not to repeat such long breaks between releases [09:22:15] yeah i was thinking we were moving too quickly for people to catch up, but leaving that long gap before 2.0 makes it harder on us [09:22:15] otherwise we'll always have some fixes we want to merge asap and differences grow [09:22:37] we can let everyone catch up after 1.10 [09:22:49] that's what you say NOW :) [09:22:54] :P [09:23:06] well then how about May 8 for 1.10 beta 1? [09:23:16] seems like we can do that pretty easily [09:23:24] yep [09:23:31] the sooner the better [09:23:39] alright [09:24:39] +1 [09:25:03] just to put a date on it, maybe an rc a week later? we can move it if there are a lot of issues [09:25:49] why not call May 8 the RC instead of beta 1? [09:26:22] I'm not sure that we're getting good testing from 2.0 final [09:26:23] only one pre-release? will it be enough? [09:26:53] depends on if it's likely to have an impact on the number of people who use it [09:26:56] yeah, not sure how many people actually use it on websites because of oldIE [09:27:03] well, technically, you'd expect 1.10 to have the same bugs as 2.0 [09:27:13] so RC seems fine to me [09:27:19] unless you live in Poland where all IEs have <18% market share ;) [09:27:22] Hey, we could move beta 1 back to May 2 if it seems everything is ready [09:27:34] that still gives us this week and most of next [09:27:37] 1.10.1 can fix the same bugs as 2.0.1 [09:28:02] so maybe we should just skip 1.10 and release 1.10.1 [09:28:02] we shoudln't ship 1.10 with bugs we can pick from 2.0.1 tho [09:28:17] nor would it even be easy to do so at this point [09:28:25] revert! [09:28:27] :) [09:28:38] intentionally revert fixes? seems extreme :D [09:28:42] fixing them earlier is fine, just saying we probably don't need to worry too much about bugs we don't know about yet [09:28:46] we put some bugs back in... happy easter egg hunting! [09:29:00] timmywil it's the bugs you don't know about that always end up biting you :P [09:29:23] 3 fixed bugs = 1 new one ;) [09:29:26] so do you want to do beta 2 on May 2 then? [09:29:30] beta 1 [09:29:32] geez [09:29:34] OK for me [09:29:53] sounds good [09:29:54] and then rc.1 later in May [09:29:58] yeah [09:30:03] see DaveMethvin, we're making good on the meeting start [09:30:16] or even final if it's really quiet on bugs [09:31:31] just putting some dates there [09:32:07] so jumping ahead to the jquery migrate bug [09:32:32] some guy wrote a blog about a bug reopened by migrate [09:32:37] link's in the issue [09:33:02] i need to re-close that ... i don't think it's too hard but i can't remember why i pulled out the check [09:33:05] i guess i'll find out [09:33:08] and explained he couldn't find a working bug tracker ;) [09:33:20] lots of lame excuses [09:33:31] but he knew how to join IRC later ;D [09:33:38] he found the migrate tracker about 5 minutes after i created the ticket [09:34:07] anyway, it kind of relates to the issues we're trying to fix with 1.11/2.1 [09:34:17] which is to make it hard to run scripts by accident [09:34:58] so Migrate will need a 1.2 version relatively soon once I fix that [09:35:24] Nobody has said that $(document.hash) is poor practice yet, right? [09:35:34] lol [09:35:39] we did, but people still do it yeah [09:35:41] ... [09:35:50] ok, just checkin [09:35:58] "jQuery: protecting people from their own stupidity since 2006" [09:36:18] it doesn't help that $() accepts just about anything [09:36:42] but i just know people are going to complain when we close their XSS holes [09:36:58] WHY AREN'T MY SCRIPTS RUNNING [09:36:58] even if we give them perfectly good ways to do things [09:37:11] it does help that we never documented any of that :D [09:37:23] laziness FTW! [09:37:59] I think some people have a problem writing $($.parseHTML(...)) instead of $(...) [09:38:14] yeah, its' ugly but if you're reading that it makes you stop and wonder [09:38:16] just as it should [09:38:35] whereas $(selector) where selector is a variable that happens to have HTML .... :) [09:38:35] $("
").html() is fine too [09:38:40] right [09:39:14] I think the main problem is $("
") [09:39:27] agreed, and if we just say we don't run scripts we can trim those spaces [09:39:29] it's common if you put inside HTML from some file [09:39:40] yeah, timmywil was right on that one and people seem to be allergic to $( $.trim(...) ) [09:39:41] yes, that should solve most problems [09:39:49] i hate when timmywil is right [09:39:53] ;) [09:39:53] :P [09:39:56] ha [09:40:07] fortunatley doesn't happen often, whew [09:40:14] yea, don't sweat it [09:40:17] okay, anybody have anything else? [09:40:31] i think we're in decent shape here [09:40:33] i"m hungry [09:40:33] just a passionate burning hatred for replaceWith [09:40:38] lol [09:40:54] gibson042 you started picking at it, and now it's bleeding [09:41:08] too late for amputation? ;) [09:41:13] the word pandora comes to mind [09:41:16] put it in an optional module [09:41:21] and then lose it [09:41:36] grunt custom -replaceWith [09:41:51] hey, worked for wrap [09:42:18] okay then, i guess we'll congregate back in -dev when needed [09:42:33] thanks guys!