#foswiki 2013-10-14,Mon

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***gac410 has left [04:01]
............................ (idle for 2h18mn)
ChanServ sets mode: +o MichaelDaum [06:19]
......................... (idle for 2h0mn)
JulianLevensI cannot create a FeatureProposal on f.o, when I click 'Create Proposal' I am offered Development.WebHome to edit, not very helpful! [08:19]
.... (idle for 19mn)
Basic proposal is for Store to accept a config hash and not use Foswiki::cfg directly: this is very useful for Store tools where multiple instances are required [08:38]
MichaelDaumJulianLevens, did you think of multiple Foswiki rather than multiple Store instances? [08:47]
JulianLevensNo I didn't, pondering ... [08:48]
MichaelDaumthough I see what you mean [08:48]
JulianLevensNo, I don't think that's appropriate. If I'm testing versatile, then I can see me testing with many different configs and many Foswikis isn't really useful [08:49]
MichaelDaumyet I would be curious in how far one Foswiki session could do away with two different Store instances referring to it in some way. [08:50]
JulianLevensOne of the main uses would be change_store anyway: ie. take existing Foswiki store convert to new Store then restart same Foswiki with new store [08:51]
MichaelDaumcreating temporary Foswiki instances ... thats happening quite frequently inside tests
heh
Foswiki feels more like Windows (rather than Linux) where you have to reboot for every little change on the system ...;)
an interesting piece of related code for you to look at is VirtualHostingContrib
it creates a local Foswiki:cfg hash by merging another one on top ... (local in the perl sense)
[08:51]
JulianLevensOK, I think I understand better what you mean. I've just looked at the change_store code which creates a FW session
OTOH, I can see this causes complications and overall it's arguably cleaner to change in Foswiki.pm "$this->{store} = $base->new();" to "$this->{store} = $base->new($Foswiki::cfg);"
Aren't multiple FW instances going to demand some monkeying around and potential headaches?
[08:54]
"$this->{store} = $base->new();" to "$this->{store} = $base->new($Foswiki::cfg{Store});" to be more precise
Actually it needs to be a copy, but you get the gist
[09:08]
........ (idle for 38mn)
***ChanServ sets mode: +o Lynnwood [09:50]
........................ (idle for 1h55mn)
ChanServ sets mode: +o gac410 [11:45]
gac410Hello all. Anyone here for the 1.1.9 release meeting? [11:53]
jastI'm here for unrelated reasons ;)
I suppose I'll chime in, time permitting
[11:56]
gac410So far the enthusiasm is deafening :) [11:57]
tsnfoogac410: sorry, got to work later than expected :-( [12:07]
gac410np [12:07]
jastwell, I'm here, that's more than I promised :}
quite possibly the other time works better for more people
[12:08]
gac410yeah, I'll be there for the other slot as well. There were no replies to the email, positive or negative. [12:09]
jastyou mainly wanted to go through items, right? including those not on the list yet that people might bring up during the meetings
well, I can't think of anything that isn't already prioritized
[12:10]
tsnfooI plan to lurk here all day... [12:11]
gac410yes. There have been no task escalations that I've noticed. [12:11]
tsnfootsnfoo browsing TsksByRelease... [12:11]
fsfsgac410: were you going to do any more work on the Maketext issue / workaround (Item12420)?
so far it's only being ignored, I seem to remember
[12:12]
gac410I think it's being solved by debian. I think that they have bumped the release of maketext
pharvey was tracking it for a while.
I'm not sure what we should do, as the distribution(s) is/are breaking the version # of a package,
[12:12]
tsnfooThere are a couple of new/confirmed tasks tagged against 1.1.9. Should we bump those, if no work has been started yet? [12:14]
jastall in all the list of tasks for 1.1.9 is looking pretty good [12:16]
gac410Item12524 - no work done. Item12577 - MichaelDaum is working on
I wish foswikibot would come back ... Babar too :)
[12:16]
MichaelDaumgac410, hi there.
bout time now?
[12:17]
gac410I guess so. [12:18]
jastI'll try and set aside some time for looking at Item12027, currently planned for minor rather than patch, but would be nice to get that fixed sooner rather than later [12:18]
MichaelDaumargh, my timezone calculator sux then [12:18]
tsnfooI vote we bump Item12524. It's probably easy to fix, but I'd rather see a 1.1.9 RC.
tsnfoo also misses foswikibot
[12:18]
jastit's not _that_ easy to fix if we don't wanna break compatibility [12:19]
MichaelDaum20:00:00 GMT UTC. thats not now, is it? [12:19]
jastno, but 12:00:00 UTC is :)
(well, half an hour ago really)
[12:19]
MichaelDaumoshit
sorry for being late
[12:20]
tsnfoolol [12:20]
gac410np [12:20]
jastwell there are two times, so technically you're not late if you are on time for the other one :) [12:20]
MichaelDaumso where are we in the agenda?
sorry having to ask. just need a quick sync
[12:21]
jastgoing through unfinished items scheduled for 1.1.9 [12:21]
MichaelDaumwhich one is next? [12:21]
gac410There are only two or 3 iirc. [12:21]
jasttsnfoo just suggested postponing Item12524 (your CompareRev template item)
yeah, not a lot
[12:22]
MichaelDaum+1 on postponing
ugly but meh
[12:22]
gac410Item12589 - login with get url - is fixed. I need to change status [12:22]
tsnfooMicha: what about Item12299 (don't rewrite the parameter list of named sections in template topics)?
If you haven't started, maybe we should postpone that as well.
[12:23]
MichaelDaumthat's a small change that I've been discussing with CDot [12:23]
tsnfooAh, reading rest of thread now [12:23]
MichaelDaumworks fine. [12:23]
gac410It's listed as an enhancement, so I'd be inclined to not want it in 1.1.9 [12:24]
tsnfooCool. Could you check that in? [12:24]
MichaelDaumI will impl it asap on rel-branch [12:24]
gac410Bug fix only ... if possible [12:24]
tsnfoogac410 raises a good point. [12:24]
MichaelDaumit really generates lots of noise for new users creating topics from templates with section markup in it ...
if you feel uneasy about it, I am okay with another post-pony
[12:24]
tsnfooProbably better to err on the conservative side for a patch release. [12:26]
MichaelDaumokay no problem
will flag the task for 1.2
done ... waiting for release of 1.2.0 now
[12:26]
tsnfooThe next new item is Item12577: deprecate jquery.tooltip. Looks like it has some commits. How far along is that, Micha? [12:27]
MichaelDaumthat was my once and only biggest issue to get that into 1.1.9
all jQuery changes on 1.1.9 have been gathered under http://foswiki.org/Tasks/Item12601
[12:28]
tsnfooAre the namespace issues resoleved by your commits, or does someone need to validate ImagePlugin? [12:29]
gac410A bunch of checkins went against Item12596 I guess by accident though [12:29]
MichaelDaumno not by accident. these where docu changes.
ImagePlugin changes are done over here locally, as well as related changes in NatSkin and ClassificationPlugin and a few others
which all are wainting for a JQueryPlugin 4.90 now
[12:29]
gac410Ah,... okay I thought they were JQuery changes.. [12:30]
tsnfooSounds like lots of dependencies there. I'm happy to help test once every things' checked in. [12:31]
MichaelDaumI will release new plugins as so as soon as 1.1.9 is out
the problem was a namespace conflict between jquery.tooltip (non jquery-ui, unmaintaned, less fancy) and jquery-ui's tooltip component, both called $.tooltip()
depending on the libs being loaded into the pages head, things could go wrong either way
[12:31]
gac410http://foswiki.org/Tasks/Item12594 I just marked waiting for release. It had a huge performance / memory impact [12:33]
tsnfooAh. I alway just manually load qtip, so I guess I've never run into that. [12:33]
MichaelDaum12594 sounds like a real important one
good to see somebody still is looking at %SEARCH code
[12:33]
tsnfooI think one of my users had hit that, but I never reproduced it. Good fix. [12:34]
MichaelDaumwas it the files-only bug? [12:35]
gac410I'm surprised nobody noticed that issue. I still don't understand why *any* meta in a keyword search didn't trigger it. [12:35]
jastso, we're postponying the CompareRev issue? :-)
I'm gonna update the Item them
[12:36]
gac410No, a leading slash in a keyword search would cause exponential escaping of the meta char, chewing up memory. Each search hit escaped all the escapes. [12:36]
MichaelDaumoic [12:36]
tsnfoojast: awesome, go ahead. [12:36]
jastwhat do we do about the MAKETEXT message? change it? add a config setting as suggested in the comments?
( http://foswiki.org/Tasks/Item12420 )
[12:38]
gac410I really hate that bug ;) [12:38]
jasta straightforward change would be to include something like "your distribution may have fixed this issue without updating the version number, feel free to check their changelog"
I feel that that's sufficient. looks ugly, of course, but we can't do everything, right?
[12:39]
gac410Yeah... I think that is reasonable. I hate to spin lots of cycles on an issue that will eventually go away, and is not really due to our code. [12:40]
jastI'm going to cook something up real quick [12:40]
gac410Basically we have to code the exploit into a checker, try it against Locale::Maketext, and warn if it's already fixed with the wrong version. Then decide, do we "turn off" our own fix, since it causes double-escaping. [12:42]
MichaelDaumthe other option is to improve the fix
not depending on whatever is in Locale::Maketext
I've solved the very same issue differently in MultiLingualPlugin's %TRANSLATE
[12:42]
gac410how? [12:43]
MichaelDauminstead of going thru another escape hell, I've limitted the functions allowed to be called within a maketext string to those needed
I borrowed some code from Locale::Maketext parsing the string
and removed the part that allowed to call pretty much any function loaded to perl
[12:43]
jastpersonally I wouldn't be opposed to a change like that [12:44]
gac410er... that's not the bug
Even if you make NO perl calls, quotes in the string to be translated can be executed
[12:44]
jastbut it's not the official syntax for function calls that creates the issue
('official' as in 'supported by Locale::Maketext even if not documented')
[12:45]
MichaelDaumhere's the relevant code http://trac.foswiki.org/browser/trunk/MultiLingualPlugin/lib/Foswiki/Plugins/MultiLingualPlugin/Core.pm#L81 [12:45]
cdotcdot just got connected; what did I miss? [12:45]
jastjust postponying all kinds of tasks
we're talking about http://foswiki.org/Tasks/Item12420 right now
(MAKETEXT fix vs. distributions that don't bump the version number)
[12:46]
gac410MichaelDaum: there are two separate exposures. One is passing functions as arguments. The 2nd is that Maketext will "eval" the string, and ` ' " can cause the eval to execute code in the string itself.
I got caught by that too. The first CVE only fixed one, and we had to re-issue a 2nd try.
[12:47]
tsnfooIs that something that can addressed in time for a 1.1.9 RC? [12:48]
jastthe security-relevant stuff is already fixed [12:48]
cdotmaybe I'm missing something, but I'd say "document it and move on" [12:48]
gac410The exposure is fully addressed. The issue now is that Debian patches it without bumping the version, So Maketext escapes, and we detect the "bad" version and also escapes, which will end up with escapes displayed in the translated string. [12:49]
jastthat was my suggestion... I'm writing a patch right now [12:49]
cdotwe cannot be expected to nursemain debian. We are doing the best we can; 'nuff said. [12:49]
gac410+1 [12:49]
jast<br> in a checker message should be fine, yes? [12:49]
cdotI wiuldn't even go thaat far. Release notes. [12:50]
jastwe thought it might be worth mentioning because the existing checker throws an error on many distributions even though there is actually no security issue [12:51]
gac410yes. cdot, the issue is the checker warns that Locale::Maketext might be vulnerable. So it should also say that your distribution might have made a bonehead move too. [12:51]
cdotfair enough [12:51]
tsnfooSo, does that cover everything except Item12596 (Documentation changes for 1.1.9)?
Or does MichaelDaum need to checkin anything to facilitate testing Item12577 (deprecate jquery.tooltip)?
[12:55]
MichaelDaumno I am done with my checkins [12:56]
tsnfooCool [12:56]
MichaelDaumdid we come to a conclusion wrt maketext?
what item is next
[12:57]
tsnfooThat may be it...
Can I mark Item12577 as Being Worked On?
[12:57]
MichaelDaumtsnfoo, no I'll separate out the ImagePlugin stuff in a separate task and flag it to waiting for release.
... which I just did
[12:58]
tsnfooSweet. I'm happy to help test anything, just let me know what versions of aha to compare. [12:59]
gac410maketext, jast will change checker to better document boneheaded distributions. [12:59]
MichaelDaumtsnfoo, thanks in advance :9 [12:59]
gac410right jast ? ;) [12:59]
MichaelDaum)
gac410, how do we deal with http://foswiki.org/Development/ReleasePlan
it seems as if we see the light at the end of the 1.1.x tunnel
[12:59]
cdotjust reading 12488..... deffo not a release blocker, IMHO [13:01]
MichaelDaumcdot, did you really mean http://foswiki.org/Tasks/Item12488 ? [13:02]
cdotno, I meant 12448
WYSIWYG bug
[13:02]
MichaelDaumah that one, umpf. [13:04]
gac410It's an annoying one though, as more and more of table attributes move to styles, they "get lost" [13:04]
jastgac410: yep
in our wikis we have stopped filtering styles/classes for tables
[13:04]
MichaelDaumwe need a priority=ugly [13:04]
cdotyes, someone needs to look at it, but it's not a release blocker imho [13:04]
jastthat is, we don't convert those back to TML [13:04]
tsnfooMichaelDaum: LOL [13:04]
jastbut HTML tables + TML = :( [13:04]
gac410I tried to add style to the STICKYBITS setting but it didn't work for me. Jast, do you have a way to do that [13:05]
MichaelDaumjast, thats a logical step [13:05]
tsnfooThis is why I don't trust my users with WYSIWYG's [13:05]
cdoty; interesting to see that wikipedia have stopped plugging it too [13:05]
jastjust discovered a new case of WysiwygPlugin screwing up today [13:05]
cdotit's a must-have, but no-one really wants top use it [13:06]
jastWYSIWYG is wonderful... until you have to convert stuff
the big issue here is that the conversion is lossy
[13:06]
gac410Jast, I tried changing STICKYBITS to include:
TABLE=align,bgcolor,frame,rules,summary,style,width;
but style still doesn't prevent conversion back to TML
[13:07]
jastwe probably changed it in an ugly way [13:07]
cdotyup. Life's a bitch. Store topics in HTML (or XML) is the only solution to that. [13:07]
MichaelDaumthe wysiwyg debate is quite controversial all over the net.
but not something we should follow up to now
[13:08]
tsnfooMichaelDaum ++ [13:08]
MichaelDaumcdot, yep: and have a pluggable renderer (tml, html=nop, xslt, foobar) [13:09]
tsnfooSo, I just noticed the couple other issues hanging out ReleaseBlockers (I was looking at TasksByRelease).
Do we need to move/update any of those?
Also, can I change that page to not say there won't be a 1.1.9? :-)
[13:09]
MichaelDaumtsnfoo, which page? [13:10]
tsnfooReleaseBlockers says there won't be a 1.1.9
Just trying to make some of these topics jive with the current reality.
[13:10]
MichaelDaumyea go ahead, please. [13:11]
tsnfooSmeone earlier mentioned that ReleasePlan has also drifted away from the current reality a bit. [13:11]
MichaelDaumhttp://foswiki.org/Development/ReleasePlan [13:11]
tsnfoogac410: Do you still think we could have a 1.1.9 RC this month, and ship in November? [13:13]
gac410tsnfoo: unless something comes up, I don't see why not. Ah... strings and translations. [13:14]
tsnfooBlarg. [13:14]
cdotwhat are the constraints? Are we depending on anyone outside this group? [13:14]
gac410I need to run a maketext run, to see if there are many changes. That's the only other constraint. [13:14]
cdothow about translations? [13:14]
gac4101.1.8 didn't have a translation run, there were 3 untranslated strings.
Not sure of current state.
[13:14]
cdot3 is survivable. [13:15]
gac410Not many changes to strings in 1.1.9, (I hope) so it should be in similar state. I never can remember how to run maketext [13:15]
tsnfoo3 would be survivable. If we really need them, my office is one floor below the madern languages department of my university. I can always go begging for translations :-)
a/madern/modern/g
Ack. Need more coffee.
[13:17]
gac410running xgettext now
okay - I've checked in the string changes. checktranslations claims 2 un-translated. Let's hope pootle tasks are still running and it sees the changes.
Without Babar, if this doesn't work I have no idea how to deal with it.
[13:18]
MichaelDaumlet's collect the remaining todos
(1) check strings and decide on translations required
[13:25]
jasthow's this look? http://awesomescreenshot.com/0801tu0of3 [13:25]
gac410translate.foswiki.org shows no changes. So I have no idea if it's not working, or if there were no changes in 1.1.9
jast, looks good to me
[13:26]
cdotyes, reads fine [13:30]
jastcommitted to both branches [13:32]
cdotdoes anyone have windows 8? Just reading http://foswiki.org/Tasks/Item11615 [13:35]
tsnfooI can setup a VM if we need to test it. [13:38]
jastI added a comment
the Maketext issue is now set to WfR
so, excluding the docs item, 1.1.9 is currently complete \o/
[13:39]
gac410There is also a twisty issue ... Expand All / Collapse all actually it a Toggle all,
http://foswiki.org/Tasks/Item12597
[13:40]
jastI looked at the JS code and I don't understand why that happens
(but I can reproduce it)
[13:42]
gac410Same here - I've reproduced it on trunk and release11 on foswiki.org. Just using the System/TwistyPlugin [13:47]
cdotbummer
it's not a blocker, but it would be nice to fix it
[13:49]
gac410yes indeed. I can imagine it being really annoying for a large doc with lots of hidden sections. [13:50]
jastI'm gonna hook up a JS debugger for this [13:51]
gac410I was hoping the reporter would look into it, yahoo does have resources, but no go. :( [13:51]
jastthis is actually relevant for one of our customers, so I think I can justify the time spent [13:51]
***cdot has left [13:54]
gac410cool, thanks jast [13:54]
jastslightly breaks, too
in my test, on one twisty it toggles the twisty content but not the twisty button
[14:00]
.... (idle for 17mn)
thing is, the code doesn't look _that_ complicated... it shouldn't really be able to hide a bug like this [14:18]
tsnfooMichaelDaum: I'm using DBRECURSE for the first time in a wiki app. OMG is this nice. [14:19]
MichaelDaumyw :)
tsnfoo, but mind you. this is THE gun for shooting your foot.
[14:20]
tsnfooLOL. Indeed. [14:21]
MichaelDaumas students say in germany: rekursiv geht schief [14:21]
tsnfooI've gotten pretty good at blowing up foswiki installs over the years, so I'll try to be careful with this :-) [14:22]
MichaelDaumadds yet another way to do so ...:) [14:22]
tsnfoo:-) [14:23]
jastit's pretty easy to write a topic that freezes the CGI, even without any plugins [14:24]
tsnfooAnybody here tried Babar's vagrant install? I was hoping to try that for testing, but it seems to die at the clone/install phase. [14:24]
jastI think someone else had a similar issue, don't recall the conclusion though [14:24]
tsnfoojast: I could make an olympic sort out of maxing out the CPU on my wiki instances ;-)
sport, that is.
[14:25]
jastI can do it with a single IF statement. ay!
*yay
[14:25]
MichaelDaumgac410, let's say the release meeting is over?
I still have no clear picture or a resumee of remaining todos up to the point of 1.1.9 being out in the wild
[14:26]
gac410MichaelDaum: Yes. Meeting adjourned. I'll be online for the 20:00 UTC - about 5+ hours from
MichaelDaum: Translations (if pootle works), Item12597 if jast makes progress otherwise defer.
If anyone online can finalize a translation, please try one of the outstanding on translate.foswiki.org And we'll see if the auto-checkin works.
Otherwise I suspect we need Babar and may have to defer.
I don't think we have any other blockers. I could probably generate a beta later this week. Or maybe do a private build to load on Foswiki.org for the first try.
[14:27]
tsnfooIt might be worth a quick scratch-and-sniff test, if you're able to set it up. [14:33]
MichaelDaumMichaelDaum tries to log in to http://translate.foswiki.org/ ... and was assuming the same creds as on f.o ... but that didnt work out [14:33]
gac410Hmmm no idea really. Just checked my own login and it's different creds. Want me to reset your password? [14:35]
MichaelDaumpootle's translation memory seems full of link spam :( [14:42]
gac410how the heck is that happening. Yech.
Where do I see that, and can it be tracked to a user?
Ah... the suggestions.
At least they don't go anywhere automatically
Maybe we have to turn off suggestions
Okay ... user "nobody" is not allowed to make suggestions.
now we need to clean up probably 1000's of spam suggestions.
[14:42]
jastseparate account system, right? [14:49]
gac410yes [14:50]
jastjust signed up [14:50]
gac410As a registered user you're allowed to make suggestions. It's up to the "lead" for each language to promote you to actually accepting translations [14:51]
jastif there's any way I can help cleaning up, let me know [14:51]
gac410I stay waaaay away from translations. Languages are definitely not my strong point. [14:52]
jastjust getting rid of the spam, I mean
I don't see any option for doing that, though
[14:52]
gac410I'm not really sure, but I think we need to add you as a reviewer for each language to clean up, then cycle through all the pending translations, and delete the spam / accept legitimate suggestions. [14:53]
MichaelDaumhow can I save a translation. I tried to translate "(disabled)" to german but I don't see a save button. clicking next and the prev shows the old wrong/fuzzy translation. what am I missing? [14:55]
gac410First ... make sure you are in project "Foswiki", not "Everything Foswiki" which is a bogus project [14:55]
MichaelDaumthen I clicked on 3 strings need your attention [14:56]
jastMichaelDaum: unless you're a reviewer already you probably have to use the 'suggest' button [14:56]
MichaelDaumdid so.
and whats next
[14:56]
jastyeah, and now a reviewer needs to accept your suggestion [14:56]
gac410Ah... MichaelDaum you are not listed as a reviewer. Only OliverKrueger and AndreUlrich [14:56]
MichaelDaumgawd [14:57]
gac410Michael, I just gave you translation rights
Not sure if you have to log out/in to acquire them.
jast: ... I just added JanKrueger as a translator too.
[14:58]
jastcheers
Bulgarian seems to have a lot of spam... I can help delete that if you give me rights there, too
[15:00]
gac410jast, should I mark the twisty bug as being worked on for 1.1.9 [15:01]
jastwell I'm not really finding any cause for the bug [15:02]
gac410Done
er... Done on Bulgarian, :( on the twisty bug
[15:02]
MichaelDaumgac410, thanks [15:05]
jastscrubbed the first 200 strings in BG [15:12]
gac410I've scrubbed spam from a bunch of others. Looks like I can update even without being a project member. [15:13]
jastaaand... BG is clean [15:17]
gac410Looks like its alphabetically the first languages gathered the most spam suggestions. [15:18]
jastthere seem to be quite a few legitimate suggestions from nobody, too
in Chinese, for example
[15:18]
gac410yes. We do need language leads to actually work on this stuff. [15:18]
MichaelDaumgerman translations are a bit off in places [15:19]
gac410Russian is a mess of spam too [15:19]
jastthere are some in Dutch, too [15:20]
MichaelDaumcan't we delete the nobody account and with it all suggestions? [15:20]
gac410Nah, I just changed nobody to not permit suggestions.
nobody is "not logged in" so the account is always there.
But we can turn of the permissions for it, which I've done.
Hm... I thought I addressed Dutch.
MichaelDaum: jast Don't spend too much time on translations until we see the background task run, If it's not going to auto-checkin to svn, then we are toast without Babar
[15:21]
MichaelDaumokay I'll stop here [15:26]
gac410I can't remember the run frequency. I'll have to check crontab
*/4 so 4 times a day?
1 */4 * * * so hours - every 4 hours?
I have to look up crontab every time I touch it - once a year or so :(
If I've done my math right, that should be 1601 GMT, so about 15-20 minutes from now.
[15:26]
..... (idle for 21mn)
MichaelDaum: jast: the translation process worked - Looks like it just checked in your work. [15:52]
jastI didn't actually really do any work [15:52]
gac410Well then MichaelDaum only [15:53]
jastor, well, I didn't do anything that could get committed [15:53]
MichaelDaumMichaelDaum maintaining an innocent face [15:54]
.... (idle for 17mn)
hey guys cool to see forces being pulled together as a result of this release meeting [16:11]
gac410Yes indeed. Maybe a bit more progress at the later meetup. I'll probably be away for a few hours this afternoon. [16:12]
MichaelDaumlet's repeat this from time to time ... though this was more of a sprint than an informat meeting ... which I actually prefer. [16:12]
gac410jast, if you are spinning on the twisty issue, MichaelDaum do you have any ideas? [16:13]
MichaelDaumnope. didnt look into it frankly.
have to finish the day right now. see you tomorrow.
[16:13]
jastbye :) [16:13]
gac410bye [16:13]
MichaelDaumbye [16:14]
jastI'm gonna head out too. good luck with the second part of the meeting. [16:18]
gac410thanks jast,
and I didn't say it to MichaelDaum_ or tsnfoo, but thanks to all getting this ready to go.
[16:18]
...................................... (idle for 3h8mn)
gac410mAll waiting for release meeting. I'm ruiinig late will be on my home system in 1/2 hour or so [19:26]
tsnfook [19:27]
..... (idle for 21mn)
gac410Made it back. Phew...
Meeting started here in the logs: http://irclogs.foswiki.org/bin/irclogger_log/foswiki?date=2013-10-14,Mon&sel=32#l28
Nothing really earth shattering. http://foswiki.org/Tasks/TasksByRelease?release=1.1.9;sortcol=4;table=1;up=0 and http://foswiki.org/Tasks/ReleaseNotes?release=1.1.9
[19:48]
tsnfooReleaseBlockers still lists Item12384 and Item12438. What's up with that?
Is that just bum logic in the SEARCH?
[20:04]
gac410They are set to target n/a, and are actually trunk issues [20:04]
tsnfooAh, seeing that now. [20:05]
gac410The patch also picks up any urgents that are not targeted
er The query ...
[20:05]
tsnfooGotcha [20:05]
gac410Anyone here for the release meeting?
I updated http://foswiki.org/Tasks/ReleaseNormals to break the "Tasks that everyone forgot" apart by n/a | patch | minor | major Anything missing from 1.1.9 that's really important to you?
Right now there is one TwistyPlugin bug that would be really nice to fix, but the fix has been elusive so it will probably not make it. http://foswiki.org/Tasks/Item12597
And one Wysiwyg bug - http://foswiki.org/Tasks/Item12448 ... table attributes are being lost when TinyMCE uses styles instead of deprecated html tags.
That one would be really nice to fix, but needs someone to do so ;)
[20:13]
.... (idle for 16mn)
WikiRingBot: seen Babar [20:35]
WikiRingBotWikiRingBot hasn't seen Babar yet [20:36]
gac410gmc are you around?
I'm curious how to recreate your task http://foswiki.org/Tasks/Item12572 ... I can't reproduce it, therefor can't fix it.
[20:50]
......... (idle for 40mn)
***ChanServ sets mode: +o SvenDowideit [21:31]
.... (idle for 18mn)
gac410Well, the 2nd release meeting was a bit of a bust. Morning went well though. If anyone wants to discuss tasks for upcoming 1.1.9, give me a shout. Otherwise I'll probably build an alpha release for foswiki.org over the next few days. [21:49]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)