[12:51] *** #twiki_release: @PeterThoeny [12:51] *** #twiki_release was created on Mon Jan 29 12:51:34 2007. [12:57] *** Lynnwood has joined #twiki_release. [12:57] *** Lynnwood has left #twiki_release. [12:59] *** ArthurClemens has joined #twiki_release. [13:01] PeterThoeny: hi arthur! [13:01] ArthurClemens: hi peter [13:01] PeterThoeny: lynnwood was here for a second [13:02] *** Lavr has joined #twiki_release. [13:02] PeterThoeny: hi kenneth! [13:02] Lavr: Hi Arthur and Peter ...unessential snipped... [13:07] PeterThoeny: hmm, only three of us [13:07] PeterThoeny: feels a bit lonely [13:08] PeterThoeny: lets give it until +10 ...unessential snipped... [13:12] PeterThoeny: hmm, +11 now [13:12] PeterThoeny: i think we do not have enough folks for the post mortem [13:12] PeterThoeny: but we can coordinate the 4.1.1 release [13:12] Lavr: No. So let us talk 4.1.1. [13:12] PeterThoeny: what do you think? [13:12] PeterThoeny: ok [13:13] PeterThoeny: ok, lets start, http://twiki.org/cgi-bin/view/Codev/FreetownReleaseMeeting2007x01x29 [13:13] Lavr: I hope we all agree that 4.1.0 has some severe bugs that triggers an urgent 4.1.1 [13:13] PeterThoeny: yes [13:13] PeterThoeny: unfortunately there are some urgent ones in the pipeline to be fixed [13:13] Lavr: I want to target a release next weekend - under condition that the urgent ones are fixed. [13:14] PeterThoeny: sounds good [13:14] PeterThoeny: http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/ReleaseBlocker [13:14] PeterThoeny: shall we go through the blockers? [13:14] Lavr: Yes lets do that [13:14] PeterThoeny: Item3510 CommentPlugin templates newline issue - doc updates needed [13:15] Lavr: I will write the docs [13:15] Lavr: I just added the 4 changes I want to do [13:15] PeterThoeny: did you follow this arthur? [13:15] ArthurClemens: yes, I am back [13:15] Lavr: You agree on the decision Arthur? [13:15] PeterThoeny: kenneth and i basically decided to do the less evil on item3510: keep changed spec and document properly [13:16] ArthurClemens: yes, sounds the wise thing to do [13:16] PeterThoeny: even if it measn that 100,000 wiki champions out there need to fix their skins, twiki apps and templates [13:17] ArthurClemens: in that light it always sounds so depressing [13:17] PeterThoeny: kenneth, any pending action on this item for other folks? [13:17] Lavr: No. I will take care of what is left. [13:17] PeterThoeny: cool :-) [13:17] ArthurClemens: CommentPlugin needs to be built [13:17] PeterThoeny: Item3529 configure stores access octals as string (patch candidate) [13:17] ArthurClemens: (if the doc is updated) [13:18] Lavr: On Item3529 CC has partly fixed it tonight. [13:18] PeterThoeny: ah, yes, new commentplugin build [13:18] PeterThoeny: who is doing this? [13:18] ArthurClemens: I can do thee build [13:18] PeterThoeny: nice [13:18] ArthurClemens: the script is ready [13:18] PeterThoeny: back to 3529 [13:19] Lavr: CC has fixed so that you can again type an octal and store it and see it afterwards. [13:19] PeterThoeny: is crawford on top of it to fix it completely? [13:19] Lavr: There are two small bugs left. [13:19] PeterThoeny: ok [13:19] PeterThoeny: small bugs no release blockers? [13:19] Lavr: 1. When you save the config the message says it set the value to the decimal value. [13:19] ArthurClemens: for anyone else perhaps? [13:19] Lavr: Confusing but not wrong. [13:20] Lavr: 2. The small delta shows the default as decimal instead of octal [13:20] ArthurClemens: hmm, still code work [13:20] Lavr: Code works so what is left is not urgent status [13:20] ArthurClemens: true [13:20] Lavr: But let us see if Crawford does not fix that also. [13:20] PeterThoeny: ok, so we can live with this in case not fixed [13:20] Lavr: He kept the bug open [13:21] PeterThoeny: ---++ Item3511 Can't go to "next" screen in configure, using Win XP [13:21] Lavr: I do not have a server running XP so I cannot verify if this bug is real [13:21] ArthurClemens: I don't have XP at hand, so this is difficult to test [13:21] *** CDot has joined #twiki_release. [13:21] Lavr: Hi Crawford we are talking about you. :-) [13:21] PeterThoeny: this is reported by two persons [13:21] PeterThoeny: both on win [13:21] ArthurClemens: we are at the second round of pints [13:21] CDot: did I miss all the exciting bits? [13:22] PeterThoeny: seems to be an issue with the perl version used [13:22] * CDot was sitting in twiki_freetown, feeling very lonely [13:22] PeterThoeny: hi crawford [13:22] Lavr: We are walking through release blockers. [13:22] PeterThoeny: we are at http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item3511 [13:22] CDot: good morning! [13:22] Lavr: We are too few for post mortem. [13:23] Lavr: The tmpfile warning is not XP unique. It also shows on Linux. [13:23] PeterThoeny: question is if 3511 can be degraded to normal or not [13:24] Lavr: If would be nice if the reporter would run configure and save the html page and upload it so we can see what is missing [13:24] PeterThoeny: is new bug in 4.1, both reporters on win xp with apache [13:24] CDot: I have seen this before; trying to remember where [13:25] PeterThoeny: crawford, looking at the error message, any bells ringing? [13:25] ArthurClemens: CDot, do you have XP? [13:25] CDot: yes, I have XP [13:25] CDot: I do not see the error [13:25] ArthurClemens: cause we don't [13:25] ArthurClemens: hmm [13:25] PeterThoeny: "Subroutine TWiki::Configure::Checker::tmpfile redefined at /usr/lib/perl5/5.8/Exporter.pm line 65." [13:25] CDot: but I use IndigoPerl [13:26] ArthurClemens: the reporters have perl v5.8.7 [13:26] CDot: I have 5.8.6 [13:27] PeterThoeny: your 4.1 runs on that perl version? [13:27] CDot: the message is a red herring, BTW. it is just a warning [13:27] CDot: PeterThoeny: yes [13:27] Lavr: I also have the Subroutine TWiki::Configure::Checker::tmpfile redefined at /usr/lib/perl5/5.8.5/Exporter.pm line 65. [13:27] Lavr: So this is not the issue on XP [13:28] PeterThoeny: this seems to be a better indication: "Firefox doesn't know how to open this address, because the protocol (c) isn't accociated with any program." [13:28] * CDot is checking the logs on XP [13:28] CDot: I do *not* get a warning [13:28] PeterThoeny: possibly a "C:\somthing" instead of "http:/somthing" ? [13:28] CDot: perhaps [13:29] CDot: possibly a CPAN module version issue? [13:29] ArthurClemens: [off] not to hurry things, but I will log off in 1 hour to get proper sleep [13:29] CDot: I have File::Temp 0.14 [13:29] PeterThoeny: one reporter uses cygwin [13:29] Lavr: We need to see the actual HTML file so we can see what is wrong in the HTML source sent to the browser. [13:30] PeterThoeny: ok, we do not need to debug here, but decide on actions to take [13:30] PeterThoeny: 1. release blocker? [13:30] PeterThoeny: 2. who is investigating? [13:30] PeterThoeny: is this a relesase blocker? [13:32] Lavr: I would like to understand more from the reporter because I can answer that question. Let us write to them and ask them to save the configure file where the next does not work as sources and post it. [13:32] Lavr: Or email it if confidential [13:33] PeterThoeny: assuming we do not get the reply/time to fix, is this a release blocker? [13:33] Lavr: No because not releasing is much worse [13:33] PeterThoeny: i am not sure, both sides have arguments [13:33] PeterThoeny: not being able to install is a release blocker [13:33] CDot: I think you can only have a release blocker that is confirmed (reproducable) [13:33] PeterThoeny: but then other bugs are severe and we need a release asap [13:34] CDot: there are so many things it could be, that if you block on every report... [13:34] Lavr: 1% not being able to install vs 90% not being able to use basic features. And this can be a configuration issue. [13:34] PeterThoeny: ok, that is a convincing argument [13:34] PeterThoeny: lets degarde to normal [13:35] PeterThoeny: but try to fix if possible until sat [13:35] PeterThoeny: s/until/by/ [13:35] PeterThoeny: action item per peter: ask reporters [13:35] PeterThoeny: ---++ Item3528 BlackListPlugin: Redirects to an empty classic style screen when you get caught [13:36] Lavr: First step is to find out if it is core or BLP [13:36] ArthurClemens: did we skip Item3446? [13:36] Lavr: If core it is serious. If BLP then it is plugin. [13:36] Lavr: 3446 is ActionTrackerPlugin [13:37] CDot: it's isolated to ATP. Not a core issue. [13:37] ArthurClemens: yes, but it is in blockers [13:37] PeterThoeny: yes, an n/a for release [13:37] PeterThoeny: because atp is not part of the release [13:37] CDot: it's a blocker for an ATP release; not a core release [13:37] Lavr: Peter. You know the BlackListP.. Can you quickly find out why it does not redirect to something valid when you save spam? [13:37] CDot: right [13:38] PeterThoeny: i just tried your link kenneth, http://www.lavrsen.dk/twiki/bin/oops/Motion/ StatisticsDataPatch?template=oopsblacklist;param1=Wiki-spam%20detected:%20%22ringtones%20 scumbag%22%20is%20a%20banned%20word%20and%20cannot%20be%20saved.%20Your%20IP%20address%20 %REMOTE_ADDR%%20is%20black%20listed%20at%20the%20%WIKITOOLNAME%%20web%20site%20due%20to%2 0suspicious%20activities.%20Please%20contact%20site%20administrator%20%WIKIWEBMASTER%%20i f%20you%20got%20on%20the%20list%20by%20mistake.;param2=%5b%5bhttp://en.wikipedia.org/wiki /Spamdexing%5d%5bOK%5d%5d [13:38] PeterThoeny: url looks proper to me [13:38] ArthurClemens: I think a oopsblacklist.pattern.tmpl is needded [13:38] PeterThoeny: it should show the message with default patternskin [13:38] ArthurClemens: I can make that [13:39] ArthurClemens: still strange that no message appears at all [13:39] PeterThoeny: kenneth, can you disable the blp for a moment to see if this changes the display of the message? [13:39] Lavr: Sure [13:40] ArthurClemens: put ;skin=classic after the url and the message shows [13:40] Lavr: disabled. [13:41] PeterThoeny: no difference with/without blp [13:41] PeterThoeny: message shown with skin=classic [13:41] PeterThoeny: not shown with skin=pattern [13:41] PeterThoeny: not shown with skin=foo (aka default templates) [13:41] PeterThoeny: so it is a core bug [13:42] Lavr: That is what I thought. [13:42] PeterThoeny: of showing oops message [13:43] PeterThoeny: http://www.lavrsen.dk/twiki/bin/oops/Motion/StatisticsDataPatch?template= oopsblacklist;param1=this+is+param1;param2=this+is+param2;skin=foo [13:43] PeterThoeny: means that parameter has no influence [13:43] ArthurClemens: the error on WikiRing: http://wikiring.org/Main/WebHome?template=oopsblacklist; param1=Wiki-spam%20detected:%20%22ringtones%20scumbag%22%20is%20a%20banned%20word%20and%20cann ot%20be%20saved.%20Your%20IP%20address%20%REMOTE_ADDR%%20is%20black%20listed%20at%20the%20%WIK ITOOLNAME%%20web%20site%20due%20to%20suspicious%20activities.%20Please%20contact%20site%20admi nistrator%20%WIKIWEBMASTER%%20if%20you%20got%20on%20the%20list%20by%20mistake.;param2= [13:43] ArthurClemens: %5b%5b(Link: http://en.wikipedia.org/wiki/Spamdexing%5d%5bOK%5d%5d)http://en.wikipedia.org/wiki/Spamdexing%5d%5bOK%5d%5d [13:43] ArthurClemens: http://wikiring.org/Main/WebHome?template=oopsblacklist;param1=Wiki-spam%20dete cted:%20%22ringtones%20scumbag%22%20is%20a%20banned%20word%20and%20cannot%20be%20saved.%20Your %20IP%20address%20%REMOTE_ADDR%%20is%20black%20listed%20at%20the%20%WIKITOOLNAME%%20web%20site %20due%20to%20suspicious%20activities.%20Please%20contact%20site%20administrator%20%WIKIWEBMAS TER%%20if%20you%20got%20on%20the%20list%20by%20mistake.;param2=%5b%5bhttp://en.wikiped [13:43] ArthurClemens: ia.org/wiki/Spamdexing%5d%5bOK%5d%5d [13:43] ArthurClemens: @#$% [13:44] ArthurClemens: they probably have natskin running [13:44] ArthurClemens: it shows the raw %PARAM1% [13:45] ArthurClemens: I am still not sure if this is not just a template problem [13:45] ArthurClemens: (at least that would be the simple solution) [13:46] PeterThoeny: ok, who is going to look into this? [13:46] ArthurClemens: I can do a pattern template [13:47] Lavr: Will you take this one Arthur? [13:47] ArthurClemens: yes [13:47] PeterThoeny: nice [13:47] ArthurClemens: someone else needs to make the natskin version [13:47] PeterThoeny: and now a hot topic [13:47] PeterThoeny: ---++ Item3476 Excessive requirement on Perl v5.8.0, lowered to 5.5.3 (patch candidate) [13:48] PeterThoeny: thsi needs more work [13:48] PeterThoeny: but we definitely cannot release twiki wrequiring perl 5.8 [13:49] PeterThoeny: worst case, take out the hard requirement in configure for 4.1.1 and fix later [13:49] Lavr: 5.5.3 seems to be our of reach. Someone reported 5.6.X broken also but working on 4.0.X so 5.6.X may short term be possible to do [13:49] PeterThoeny: lets be realistic: twiki 4.0.x had no hard requirement on perl, but no tests [13:50] PeterThoeny: why not do the same for 4.1? [13:50] PeterThoeny: from this perspective this is not a release blocker if we take out the hard requirement [13:50] Lavr: Why not replace it with a warning saying - TWiki will not work on Perl versions earlier than 5.8 without upgrading part of perl or modifying TWiki. [13:51] Lavr: We also warn against CPAN libs missing or being too old but still run the configure. [13:51] ArthurClemens: Wouldn't that create a lot of support questions of users wondering why their TWiki does not work? [13:51] PeterThoeny: well, twiki 4.0.x had a "5.5.3 required, 5.8 recommended" [13:51] PeterThoeny: that looks reasonable to me (although we have known issues to fix) [13:51] Lavr: We sort of need some of those to make it work. 4.0.x for sure did not run on 5.5.3 either according to reports. 5.6.X did [13:52] PeterThoeny: yes [13:53] ArthurClemens: do we have concrete reports about 5.6.X not working? [13:53] PeterThoeny: i recommend this: 1. remove hard requirement on 5.8 2. put into configure: "5.5.3 required, 5.8 recommended" 3. test and fix for 5.6.x [13:53] PeterThoeny: and assess if we can support 5.5.3 after 4.1.1 release [13:53] CDot: I ghave experience of 5.6 *not* working [13:54] PeterThoeny: so, focus our energy to get it run on 5.6 (as twiki 4.0.x) [13:54] CDot: to claim it is, IMHO, unprofessional. [13:54] ArthurClemens: do unit tests fail with 5.6? [13:54] CDot: don't know. [13:54] CDot: I don;t have 5.6 to test. [13:54] CDot: I would be happy with a statement like this: [13:55] CDot: "TWiki is tested on perl 5.8. However it should work with earlier versions of Perl" [13:55] Lavr: It was my plan to release 4.1.1 first and then work on making some VMs we could test with afterwards. We cannot make a 5.6.X TWiki in one week without making new bugs. [13:55] CDot: I am *not* happy claiming an untested version, though. [13:56] PeterThoeny: again, "5.5.3 required, 5.8 recommended" is saying that we recomment 5.8 [13:56] PeterThoeny: if it does not work with earlier versions it is treated as a bug [13:56] Lavr: We should claim what we have tested but not let configure be hardcoded to not run. If someone hacks some solutions then it is an advantage that it runs until failure. [13:56] CDot: no, it's not. it is clearly (to me anyway) saying "we tested it on 5.5.3" which is not the case. [13:57] Lavr: We cannot say 5.5.3 required when we KNOW it does not work. it has been tested now and failed. [13:57] *** MarkKeisler has joined #twiki_release. [13:57] PeterThoeny: i see the point about claiming only tested stuff; by all means lets create that test env [13:57] Lavr: Hi Mark. [13:57] MarkKeisler: :) [13:57] MarkKeisler: saw you were 'terribly alone' :) [13:58] PeterThoeny: until then imho it is (no i am not going to say this) [13:58] Lavr: We have tested 5.5.3 and failed so we cannot claim that. We have to claim - tested on 5.8.X. May run on earlier versions with some tweaking of either Perl or TWiki. [13:58] PeterThoeny: hi mark, nice to see a new face here :-) [13:58] Lavr: And then replace the hard code by a warning. [13:58] CDot: Lavr: I'd be quite happy with that staement. It's accurate and true. [13:59] MarkKeisler: ah, the issue of requiriung perl 5.8.x? [13:59] CDot: yep, 'fraid so [13:59] MarkKeisler: for 4.1.0, i upgraded to 5.8.8 from 5.8.0 cuz core modules needed updating. [13:59] MarkKeisler: so i just built up to the latest [14:00] MarkKeisler: i may be handier with sysad stuff than the average joe twiki user [14:00] Lavr: Module updating is often needed. But here we are talking about the basic perl version 5.5 bs 5.6 vs 5.8 [14:00] CDot: ah, the main concern is with peope who are just kicking the tyres, i think [14:00] PeterThoeny: mark: just the fact that you are here makes you a geek, e.g. you are not the joe average insatlling twiki :-) [14:00] MarkKeisler: lol [14:01] ArthurClemens: possibly some providers have not updated Perl [14:01] CDot: If I had a single client on perl 5.6, I would be serious about testing on it [14:01] CDot: but I don't. :-( [14:01] PeterThoeny: no, main conern is to make it easy for unexperienced sys admins [14:01] PeterThoeny: to install twiki [14:01] MarkKeisler: start bundling perl into it :) [14:02] CDot: MarkKeisler: wash your mouth out with soap! [14:02] MarkKeisler: hehehe [14:02] PeterThoeny: the fact is that most folks installing twiki never heard of cpan, do not know perl, and never touched an apache config file [14:02] PeterThoeny: that is the real issue [14:02] PeterThoeny: more customer focus [14:02] MarkKeisler: so what would help is a smart script to help get all that stuff up to snuff [14:02] MarkKeisler: pre-install script. updates modules from cpan, etc [14:03] MarkKeisler: assuming user has admin privs [14:03] MarkKeisler: or can even install mods in homedir if not [14:03] CDot: mark, there *is* one, but it has lacked commitment from the community to test it in all envs (or even to use it) [14:04] Lavr: RIght now MY scope is 4.1.1 released in 6 days. So for now I will settle with small change in configure that warns instead of halts and mumbles something about the perl version before it dies anyway. [14:04] PeterThoeny: agreed [14:04] CDot: Lavr: that's fair [14:05] MarkKeisler: all envs, eh? damn windows... [14:05] PeterThoeny: on customer focus and types of users, see my last post at http://twiki.org/cgi-bin/view/Codev/WhatVersionsOfPerlAreSupported [14:05] CDot: eval "require 5.008"; warn "Things may go horribly wrong" if $@; [14:06] Lavr: Yes. [14:06] PeterThoeny: that is too agressive [14:06] PeterThoeny: scares off folks installing twiki [14:06] Lavr: I am sure CDot meant to put a better text :-) [14:07] Lavr: eval "require 5.008"; warn "Sod off punk" if $@; [14:07] CDot: eval "require 5.008"; warn "Check your life insurance is current" if $@; ? [14:08] PeterThoeny: eval "require 5.008"; warn "please post your social security number on twiki.org" if $@; [14:08] ArthurClemens: continue? [14:09] Lavr: "Warning. Your Perl version is older then 5.8.X. TWiki has only been tested with 5.8.X. Running on older version may require updating your Perl installation." [14:09] PeterThoeny: no, first we need to find a closure on this [14:09] PeterThoeny: and flood the error log with touusands of messages? [14:09] PeterThoeny: this is bad [14:10] Lavr: It is the message that configure should show in the browser. Where it also lists all the other CPAN modules. [14:10] PeterThoeny: or throw a warning to the user on the screen each time [14:10] PeterThoeny: this is badd too [14:10] Lavr: Naturally not in TWiki itself. It will dies anyway until people have tweaked. It is configure I am talking about. [14:10] PeterThoeny: ok, if this is shown only in configure i can live with it [14:10] PeterThoeny: just making sure [14:11] PeterThoeny: we have seen hard coded stuff before in the view script [14:11] PeterThoeny: that has been reverted [14:11] Lavr: CDot. you know what to do now? You take the action? [14:12] Lavr: With the message I suggested above? (2nd one :-) ) [14:12] PeterThoeny: i think we can agree on this now [14:12] Lavr: Item3443 SEARCH performance under mod_perl is awful [14:13] Lavr: That one is not 4.1.1. It needs more docs and more test. [14:13] Lavr: Agree? [14:13] Lavr: Next is Item3509 initializeUserHandler receives no loginName [14:14] *** RhastaW has joined #twiki_release. [14:14] Lavr: "The code line that was changed comes from SVN r11571 made by TWiki:Main.CrawfordCurrie" [14:14] Lavr: An issue for some plugins it seems. [14:15] Lavr: Hello RhastaW [14:15] Lavr: We are walking through release blockers for 4.1.1 [14:16] RhastaW: pretty sure im just here to observe ;) [14:16] PeterThoeny: ..back, sorry, interrupted by phone call [14:16] ArthurClemens: ping CDot [14:17] ArthurClemens: park this? [14:17] CDot: sorry [14:18] CDot: I'm here [14:18] CDot: it is extensively tested; it is live on 6 hot installs [14:18] CDot: however the doc is bad, i acknowledge [14:19] CDot: it can be applied as a patch, so I don;t see it as a blocker. [14:19] CDot: on the initializeUserHandler: what is the user trying to do with it? [14:19] PeterThoeny: what about the recommened fix by vernon? [14:20] CDot: erm, I;m pretty sure that is dangerous [14:20] * CDot checks the code [14:20] Lavr: I have seen many proposed fixes that breaks more than they fix. And this is related to authentication so we have to be very careful. [14:21] PeterThoeny: agreed [14:22] PeterThoeny: i suggest to not touch the code for 4.1.1 and investigate later [14:22] CDot: yes [14:22] PeterThoeny: reporter has a workaround fix for now [14:22] PeterThoeny: ---++ Item3483 Error logging in when there is apache login and DENYWEBVIEW [14:23] PeterThoeny: what is the status on this one? [14:23] Lavr: Partly fixed. [14:24] Lavr: Still two issue and one should perhaps have its own bug report. [14:24] PeterThoeny: reading http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item3483 it looks like the release blocker issue is fixed [14:24] PeterThoeny: we can live with double parameters [14:24] PeterThoeny: as normal bug? [14:24] Lavr: I am very concerned about the double parameters. I am sure it will breaks something at one point for people [14:25] CDot: ah yes.... the fix proposed for 3500 may re-enable the "log in when apache auth fails" bug [14:25] CDot: so for sure not simple to fix [14:26] PeterThoeny: so, what action should we take for 3483? [14:26] Lavr: Can someone help analysing if we can count on the URL params always being added? [14:27] Lavr: Because then it is a simple regex to remove them from the code I already fixed. [14:28] Lavr: I think it was Thomas that added the feature that URL params are carried over when redirecting, print viewing etc [14:28] PeterThoeny: out of scope for 4.1.1, we need a official function to manipulate parameters: use existing param list, replace some, remove some [14:28] CDot: yes, but removing then is treating the symptom, not the disease [14:28] Lavr: And this is probably what now creates the double url params because the login code already did this - and only in some server environments. [14:29] CDot: the login code uses the params cache; it doesn't rewrite the query string [14:30] CDot: but we need to debug this offline. I will try and find time to look into it. [14:30] PeterThoeny: ok, thanks [14:31] PeterThoeny: ---++ Item3486 Funny characters in PageNames? cause problems (patch release candidate) [14:31] Lavr: OK. Only one more to discuss maybe we can take 5 minutes afterwards so I can tell what I have observed already [14:31] Lavr: 3486 is a funny one. And hopefully just a regex fix. [14:32] Lavr: You can write [[[HelloWorld][Hello my friend]] and it creates a topic called [HelloWorld [14:32] Lavr: With the [ [14:32] CDot: pretty sure that's just a regex issue [14:32] PeterThoeny: this is a bug that needs to be fixed, but i do not think this is a release blocker [14:32] CDot: it has probably been there for a long, long time [14:33] ArthurClemens: reminder: when it is fixed the javascript check needs to be updated as well [14:33] PeterThoeny: shall we degrade to normal? [14:33] Lavr: I have seen many garbage topic names on my server and now I know why. If it is easy to fix let us fix it. [14:34] PeterThoeny: looks almost like it would be useful to have a priority between "normal" and "urgent" [14:34] Lavr: Do you already now know where to look? That is usually what takes time for me. Once I know in which source file I am able to hack a regex [14:35] Lavr: The problem with the [Hello topic is that you cannot delete it afterwards. [14:35] PeterThoeny: there is a name filter for topic names [14:35] CDot: Lavr: yes [14:35] PeterThoeny: could be a simple fix there [14:35] PeterThoeny: not sure [14:35] CDot: look in TWiki/Render.pm [14:35] Lavr: OK. Will do thanks [14:36] PeterThoeny: actually, could be in initialize of twiki.pm [14:36] CDot: sub _handleSquareBracketedLink { [14:36] PeterThoeny: where the topic name is determined (e.g. spaces taken out) [14:37] ArthurClemens: I am going to leave you all now, getting some sleep. I would appreciate if you could give your thoughts (later) on (minor) issue http://64.38.10.58/~twiki4/cgi-bin/view/Bugs/Item3530 as I have the fixes ready. [14:37] ArthurClemens: good night! [14:37] PeterThoeny: proper fix to me is more on the receiving side, e.g. a "[AnyName" topic is equivalent to "AnyName" [14:37] PeterThoeny: good night arthur, thanks for participating :-) [14:37] CDot: ArthurClemens: sleep well! [14:37] Lavr: NIght Arthur [14:38] CDot: PeterThoeny: ? [AnyName may be a valid topic name, if NameFilter includes [ [14:38] PeterThoeny: are we done with 3486? [14:38] CDot: you can't just arbitrarily rule it out [14:39] CDot: reckon so [14:40] PeterThoeny: i have never seen a topic name with [ [14:40] CDot: Lavr: TWiki:Render.pm, line 1098, change to $text =~ s/\[\[([^\][\n]+)\](\[([^\]\n]+)\])?\]/$this->_handleSquareBracketedLink($theWeb, $theTopic,$1,$3)/ge; [14:40] PeterThoeny: we recomment pure wikiwords and accept _, - and a few other chars [14:41] Lavr: CDot. Now I think I can fix it. I will test it first before checking in. Just in case. [14:41] Lavr: :-) [14:42] PeterThoeny: remaining two urgent items are of non-distrib plugins, so n/a [14:42] CDot: I find the ability to have "informal" topic names very useful in twiki apps, myself [14:42] *** ArthurClemens has signed off IRC ("Comp takes a nap"). [14:42] CDot: though that's just me [14:44] Lavr: OK. We are at the end and too little time for lessons learned and too few of the 4.1.0 developers. [14:44] PeterThoeny: arthur asked to look at 3530 [14:45] Lavr: I already did look at it. It removes the smart WebTopicCreator when creating from Jump but allows creating topics in upgraded webs without having add the WebTopicCreator to all old webs. [14:45] Lavr: Which is yet another hurdle for the upgrader and caused med a lot of pain. [14:45] Lavr: ..when I upgraded. [14:46] PeterThoeny: 3530 is something else? [14:46] Lavr: Oh. Sorry. [14:46] PeterThoeny: it looks like arthur would like to change the default search to look also in the topic name [14:48] Lavr: I would not mind. But I hate to modify WebTopBar in a patch release because this is one of the most often tailored parts of TWiki [14:48] PeterThoeny: he suggests to change the default search in WebSearch and search box on top from scope="text" to scope="all", e.g. search text and topic name by default [14:48] PeterThoeny: ah [14:48] PeterThoeny: good point [14:49] PeterThoeny: so, yes for websearch, no for search box in top bar? [14:49] Lavr: WebLeftBar, WebTopBar, WebPreferences, Main.TWikiPreferences and similar require some pretty good requirements before I will add those to a the upgrade part of a patch release. [14:49] PeterThoeny: ok, makes sense [14:50] Lavr: The Jump field is sort of the field for searching topic names. [14:51] PeterThoeny: good point [14:51] PeterThoeny: so it makes sense to have a different default search in websearch and search field on top [14:51] PeterThoeny: that's it on bug review? [14:51] PeterThoeny: i have 9 more minutes befroe the next meeting [14:53] Lavr: We can spend the last 9 for me to teel what I know about the double URL. [14:53] PeterThoeny: what else should we descuss/coordinate for release? [14:53] PeterThoeny: kenneth, before the double url, [14:54] CDot: Lavr: return to #twiki to discuss double URL when we are done here [14:54] PeterThoeny: anything that needs to be discussed in your relesae manager role? [14:54] Lavr: Normally there are not that many bells and whistles for a patch release. [14:54] Lavr: I build it. I release it on Codev. We announce it on the mailing list and in Developer News and update the t.o. where needed. [14:54] PeterThoeny: are all paches that apply in patch release? [14:55] PeterThoeny: branch i mean? [14:55] Lavr: I merge in things as they are resolved if the developer has not done it. [14:55] PeterThoeny: ok, so patch branch is up to date at this time [14:55] PeterThoeny: nice [14:56] Lavr: And I put a note in the bugs item when I do it. [14:56] PeterThoeny: do you need any help on the release? [14:56] Lavr: I think I am OK: [14:56] Lavr: The help I need is fix the bugs :-) [14:57] Lavr: Item3471 needs to be merged. [14:57] Lavr: Arthur completed that tonight [14:57] PeterThoeny: when is code freeze for 4.1.1? [14:57] PeterThoeny: sat? [14:58] Lavr: Yes. [14:58] PeterThoeny: ok, great [14:58] PeterThoeny: lets announce that in codev and #twiki [14:58] Lavr: And naturally no string changes allowed. [14:58] PeterThoeny: yes, very careful bug fixing only [14:59] PeterThoeny: ok, we are done with first freetown meeting? [14:59] Lavr: Yes [14:59] Lavr: I will minute tomorrow. I did not do it on the fly this time. [15:00] PeterThoeny: (btw, i asked for permission to use a photo of freetown on freetownrelease topic) [15:00] PeterThoeny: ok [15:00] Lavr: There were not many conclusions other than ownership of fixes. [15:00] PeterThoeny: thanks [15:00] PeterThoeny: yes [15:00] PeterThoeny: ok, thanks all for participating! [15:00] CDot: gnight! [15:00] Lavr: OK back to #twiki [15:33] *** MarkKeisler has left #twiki_release. [16:06] *** CDot has left #twiki_release.