ReleaseMeeting01x02_20140616

Details

1. Tasks review - tasks with commits

Continues from ReleaseMeeting01x02_20140602. Green shows current status (since the meeting)

  • 10009 (Closed): extract the serialisers from the QUERY macro code, and move to LegacyMeta, then implement a FastMeta that doesn't use double book-keeping; CDot and JulianLevens believe this can be deferred since it works, even if it's not quite perfect.
  • 10764 (Closed): PlainFile logger needs to open files in proper encoding to avoid "Wide character in print"; Need feedback from George as logging expert.
  • 11400 (Closed): Add default param values to TMPL:DEF; CDot looked at this in more detail and deems it release-ready.
  • 11833 (Closed): FORMFIELD does not render a field using renderForDisplay whereas SEARCH does; Michael feels there's more that can be done here but the problem as stated in the task has been fixed, so WFR...
  • 12060 (Closed): INCLUDE macros "warn" attribute does not accept dollar-escapes; straightforward to fix; looks release-ready.
  • 12093 (Closed): ship foswiki using the new logo; Michael will be changing the font and that's all that's left to do. BWO.
  • 12381 (Closed): Configure UI and help text review; this one seems focused on help texts. We'll get back to it once we've figured out what to do with the UI. BWO.
  • 12475 (Closed): Move lib/CPAN/lib modules to a separate CpanContrib; George seems to be working on this one. WFGeorge.
  • 12515 (Closed): Create a new ConfigurePlugin; !CDot's domain. BWO.
  • 12686 (Closed): add tmpl REST handler to load jquery.tmpl asyonchronously; is BWO by Michael
  • 12712 (Closed): Foswiki loggers should obtain file lock before writing; is waiting for George
  • 12839 (Closed): REST scripts should individually assert their security requirements; is waiting for CDot
  • 12849 (Closed): Implement RemoveDeprecatedEmptyDENYRule; all concerns have been resolved (though Michael notes there are potential issues with shipping wiki apps), WFR.
  • 12888 (Closed): Unit tests are failing; catch all, leave as-is.
  • 12936 (Closed): Tighten up default restrictions on WikiGuest a bit further; George? (BWO)
  • 9693 (Closed): Documentation updates for Foswiki 1.2.0; catch all, leave as-is.

That's the full list of tasks with commits that have (had) status "Being worked on". Since we're out of time, the rest will be postponed until the next meeting.

2. Tasks Review - Release Blockers

3. Tasks Review - Normal and Low priority

IRC Log

  • Started talking in foswiki-release on Monday 16/06/2014 13:58:37
  • 14:51 -> CDot has joined foswiki-release
  • 15:00 -> andreli has joined foswiki-release
  • -> ModAcOst has joined foswiki-release
  • 15:05 -> jast has joined foswiki-release
  • JulianLevens Hello
  • 15:07 jast hi! busy on other fronts right now but I'll be watching and chiming in if I have anything to say
  • 15:08 ModAcOst Hi
  • 15:09 andreli Hello
  • 15:11 JulianLevens We need someone to try running the meeting. This is 1st time I've tried to help a release, so I doubt I'm much help
  • 15:13 andreli Is there a list, preferably autimatically generated, about open bugs, blockers and change requests?
  • 15:14 -> mglAC has joined foswiki-release
  • CDot andreli: there are many lists...
  • 15:15 CDot current list of release blockers is http://foswiki.org/Tasks/MinorReleaseBlocker
  • CDot that should cover all the most recent understandings/triages/analyses
  • JulianLevens But probably doesn't
  • 15:16 JulianLevens We do have an agenda should we try and follow it?
  • JulianLevens http://foswiki.org/Development/ReleaseMeeting01x02_20140616
  • CDot JulianLevens: you have the helm.
  • 15:17 JulianLevens Driving without a license
  • jast the guy with the license is not here, so there's no way around that
  • 15:18 JulianLevens So we start with a Task review, tasks with commits
  • CDot not sure what "tasks with commits" is meant to mean.....
  • 15:19 JulianLevens Neither do I
  • jast open tasks for 1.2 that have commits on them
  • jast basically "stuff has been done but it's not complete, so let's figure out what to do about it"
  • CDot ok
  • JulianLevens Where do we find that list?
  • 15:21 JulianLevens http://www.foswiki.org/Tasks/TasksByRelease?release=1.2.0
  • 15:22 CDot It would help to have MichaelDaum here, I suspect
  • 15:24 jast I was at the last meeting, actually, as were three others present right now
  • CDot OK, I'm going to make a suggestion. based on http://www.foswiki.org/Tasks/TasksByRelease?release=1.2.0 there are a number of tasks marked "Waiting for Feedback". propose we review those, and identify any that can be kicked.
  • jast but we didn't get started the 'tasks with commits' thing IIRC
  • JulianLevens http://www.foswiki.org/Tasks/TasksByRelease?release=1.2.0;withcheckins=1;sortcol=4;table=1;up=0#sorted_table
  • 15:25 -> MichaelDaum has joined foswiki-release
  • MichaelDaum hey there. sorry for the delay. phone calls all over me.
  • jast I propose we defer anything that isn't a blocker that hasn't been worked on at all so far
  • JulianLevens That last list is manageable
  • 15:26 JulianLevens There are 16 items to consider
  • jast add a ;state=open to that list for more manageableness
  • jast okay, that doesnt' actually work, never mind
  • CDot I don't mind; either "Being worked on" or "Waiting for feedback" are good places to start
  • 15:27 CDot suggest "waiting for feedback" is a procedural problem; viz. how do we kick the people that feedback is wanted from?
  • jast "being worked on" just as much if the person is MIA
  • 15:28 CDot indeed
  • 15:29 jast starting with the first one in the list: Item10009, extract the serialisers from the QUERY macro code, and move to LegacyMeta, then implement a FastMeta that doesn't use double book-keeping (SvenDowideit)
  • CDot I believe that the serialiser separation that is in there is working, and while it is less than perfect, it can be deferred.
  • 15:30 JulianLevens I agree
  • CDot The "double book-keeping" is really a performance issue, down to legacy code
  • 15:31 CDot Action: defer 10009
  • JulianLevens Noted
  • CDot Next, 10764
  • CDot PlainFile logger needs to open files in proper encoding to avoid "Wide character in print"
  • MichaelDaum any list you are proceeding along?
  • jast is someone taking minutes?
  • jast MichaelDaum: http://www.foswiki.org/Tasks/TasksByRelease?release=1.2.0;withcheckins=1;sortcol=4;table=1;up=0#sorted_table
  • 15:32 CDot MichaelDaum: yes jast: no
  • jast I'll do minutes
  • CDot jast: thanks
  • -> Lynnwood has joined foswiki-release
  • 15:33 MichaelDaum wondered where 10764 was on http://foswiki.org/Tasks/MinorReleaseBlocker
  • CDot it isn't a blocker. It's a Task logged for completion in 1.2.0
  • CDot it's status Normal
  • 15:34 JulianLevens So defer again?
  • CDot according to the agenda, we review these tasks with commits first, and then release blockers
  • CDot didn't make the rules
  • 15:35 CDot JulianLevens: I think that has to be made "Feedback by gac410", as George is Mr Go-To for loggers.
  • JulianLevens Makes sense
  • 15:36 JulianLevens Moving on to Item11400
  • 15:37 JulianLevens (please shout if you want to say more about a Task)
  • jast it's not clear whether 11400 is ready for release
  • jast does anyone want to volunteer to look at this in more depth?
  • 15:38 CDot is reading code, but can't see any unit tests, or even where the code is that handles this
  • jast lib/Foswiki/Templates.pm
  • jast http://trac.foswiki.org/browser/trunk/core/lib/Foswiki/Templates.pm?rev=13537
  • 15:39 CDot carry on, leave it with me and I'll report back shortly
  • JulianLevens Great thanks
  • JulianLevens NEXT: http://www.foswiki.org/Tasks/Item11833
  • 15:40 JulianLevens This clearly requires CDot and MichaelDaum
  • jast paging Dr Daum
  • CDot ok, I have reviewed 11400 and I'm happy for it to be moved to "Waiting for Release"
  • 15:41 MichaelDaum me 2
  • jast great
  • MichaelDaum CDot, did you read my last comment?
  • MichaelDaum arh phone again
  • CDot MichaelDaum: the "WTF?" comment? Yes.
  • 15:42 CDot BTW, WTF == "Where's The FeatureRequest "
  • MichaelDaum naw the last one on http://www.foswiki.org/Tasks/Item11833
  • CDot reading
  • CDot just catching up
  • 15:46 CDot MichaelDaum: I don't fully understand the problem, without diving into code, but I think there's a general principle we need to adopt here; let's look forwards, and not back. OK, so some existing plugins may need to change - I strongly suspect you already dealt with them. But is what we have now in the core the right way to move ahead or not?
  • MichaelDaum so far I've found a way to work with it
  • 15:47 MichaelDaum I could imagine a better way to render the display widget
  • MichaelDaum but frankly I didn't make up my mind in enuf detail really
  • 15:48 JulianLevens Does what we have merit becoming WFR?
  • MichaelDaum just imagine the situation: a formfield renders it's value using a more complicated way than just mapping between data model and visible item ... e.g. consulting a database backend and render a statistics distribution in a select+social formfield.
  • 15:49 JulianLevens Sounds cool; but do we need to finish that this release?
  • MichaelDaum that's what I was working on at that time: SocialFormfieldsPlugin (formfield values per user, displayed as a statistics color bar), PasswordPlugin (fetch values from a distant db while encrypting/decrypting raw values)
  • 15:50 MichaelDaum there's much more that we need here far exceeding 1.2
  • JulianLevens OK, what we have a good step forward but not a bad foundation for the future, so we mark as WFR?
  • MichaelDaum once I know what I am doing I'll create a proposal for it
  • 15:51 JulianLevens I look forward to that
  • 15:52 CDot I think we should WFR this current task, and let Micha develop a feature request.
  • MichaelDaum wfr the current work done on 11833 as it clearly addresses the outlined issues so far
  • JulianLevens Great, another one bites the dust
  • JulianLevens http://www.foswiki.org/Tasks/Item12060
  • 15:53 CDot 12060 should be boosted to a release blocker. It's nasty.
  • CDot the more we can stanrdise the escapes, the better.
  • MichaelDaum yes, George and I were discussing warn="$percntINCLUDE{SomeOtherTopic}$percnt" recently...
  • 15:54 MichaelDaum didn't he implement it already?
  • 15:55 MichaelDaum oh yea
  • andreli There is some code that looks reasonable.
  • JulianLevens He may have done, but he has left it marked BWO, are there unit tests?
  • MichaelDaum http://trac.foswiki.org/changeset/17739
  • CDot yes
  • MichaelDaum and http://trac.foswiki.org/changeset/17742
  • 15:56 MichaelDaum so the tests cover std esc
  • CDot WFR it, it's done IMHO.
  • CDot 12093, the new logo
  • 15:57 MichaelDaum there's a todo for me: improve fonts
  • CDot really?
  • 15:58 CDot really really?
  • MichaelDaum got the svg over here using arial instead of this serif font. what follows is png-ing it
  • MichaelDaum note to myself: don't forget about configure
  • jast Arial isn't that beautiful either
  • 15:59 MichaelDaum it is good enuf for the logo
  • CDot Comic sans!
  • jast if you're going to look at it anyway, I suggest looking at Free fonts (e.g. DejaVu, Linux Biolinum)
  • MichaelDaum there's no lengthy copy in the logo which would unveil the weaknesses of arial, so ...
  • jast just for the philosophical side
  • 16:00 jast I don't have strong feelings about the font at any rate
  • MichaelDaum the main pro for arial in the logo is compatibility with webdesigns where the logo occurs.
  • jast I just happen to like Biolinum rather well
  • jast well, these super-thin fonts are all the rage today. arial doesn't work well with those. you can never really make it work everywhere.
  • 16:01 MichaelDaum definitely not.
  • JulianLevens So from a release point of view, what's the action?
  • MichaelDaum at the end it is just "Foswiki" to be rendered in a good-enuf font
  • jast might even reuse the current logo's font, for consistency and all that
  • MichaelDaum BWO
  • 16:02 jast so, leave as is
  • jast (the task)
  • JulianLevens And now the smallest item on the list http://www.foswiki.org/Tasks/Item12093
  • MichaelDaum http://foswiki.org/pub/Community/BrandLogoTalk/foswiki-logo-arial.svg instead of http://foswiki.org/pub/Community/BrandLogoTalk/foswiki-logo-final.svg
  • CDot can it
  • 16:03 JulianLevens Sorry that should have been: http://www.foswiki.org/Tasks/Item12381
  • CDot what happened to 12160?
  • 16:04 jast this should be postponed until we've figured out what to do with Configure
  • jast CDot: no commits on that one
  • CDot ok, so it should just be closed No Action
  • jast I don't even know what 12160 is about. the task is way incomplete.
  • 16:05 jast close or defer?
  • CDot close, no action. Insufficient detail.
  • MichaelDaum +1
  • jast actually the agenda forbids dealing with this right now
  • jast
  • 16:06 MichaelDaum why's that?
  • jast no commits. we're going through the list of tasks with commits right now.
  • CDot too late, someone closed it offline.
  • jast I'll just not include it in the minutes
  • CDot ok
  • 16:07 jast 12381... postpone until we've figured out configure's UI?
  • CDot yes
  • 16:08 jast http://www.foswiki.org/Tasks/Item12475 - CpanContrib
  • CDot yup - it needs a "WaitingFor"
  • 16:09 JulianLevens Sorry, but by postpone you mean leave Item12381 as BWO and come back to this at another meeting?
  • jast JulianLevens: yes
  • CDot can't have a task in wait state without someone it is waiting for
  • JulianLevens OK
  • jast CDot: which one, configure or cpan?
  • CDot cpan
  • 16:10 CDot configure is waiting for the "Configure team" - me, you, gac410
  • CDot and anyone else with an itch
  • jast okay. who is cpan waiting for?
  • CDot dunno; that's why I asked
  • jast I've seen oliver and george involved in that one, I think
  • 16:11 JulianLevens Oliver did stuff at the Camp and George picked it up later, I think CDot helped Oliver at the Camp
  • 16:12 CDot nope, not me
  • jast George was the last person to touch this one. I think we'll want to ask him what plans/goals he has.
  • CDot threw a few ideas his way, but no more than that
  • 16:13 jast leave at BWO IMO
  • 16:15 JulianLevens What about the WaitingFor field?
  • CDot fling it gac410's way; he was last seen thinking about it
  • 16:16 CDot and he's not here to defend himself
  • JulianLevens OK, moving on: http://www.foswiki.org/Tasks/Item12515
  • 16:20 CDot as 12381. Waiting for me.
  • 16:22 JulianLevens OK, http://www.foswiki.org/Tasks/Item12686
  • CDot MichaelDaum: ?
  • MichaelDaum clicks
  • MichaelDaum feature finished. needs docu.
  • 16:23 MichaelDaum waiting for me
  • 16:24 JulianLevens http://www.foswiki.org/Tasks/Item12712 is another Logger item so leave the Task as is Waiting for gac410
  • 16:25 JulianLevens http://www.foswiki.org/Tasks/Item12839
  • 16:26 JulianLevens MichaeDaum can you comment on this?
  • 16:28 MichaelDaum remaining work is on NatEdit
  • MichaelDaum and some non-core plugins
  • CDot you can set that waiting for me. I didn't know about it.
  • CDot (MailerContribPlugin, that is)
  • 16:30 MichaelDaum checked in the natedit fixes
  • MichaelDaum not looked at UpdatesPlugin for a long time
  • 16:32 JulianLevens So, Item12839 left as-is except the addition of CDot as waiting for?
  • CDot guess so
  • 16:33 JulianLevens OK, we then have http://www.foswiki.org/Tasks/Item12849
  • CDot dunno why that's waiting for me
  • CDot no idea what I'm supposed to do with it
  • 16:34 JulianLevens MichaelDaum asked about possible WebDav implications
  • MichaelDaum right
  • CDot OIC; there should be no implications; FilesysVirtualContrib uses the offical FW APIs for access controls, so should simply reflect them
  • 16:35 MichaelDaum ah ok. good.
  • 16:36 MichaelDaum so WFR
  • JulianLevens Excellent
  • JulianLevens http://www.foswiki.org/Tasks/Item12888
  • MichaelDaum one last note on 12849: shipping wiki apps with ACLs applied might cause incompatibilities
  • 16:38 jast 12888 is a catch-all, leave unchanged
  • JulianLevens jast, agreed'
  • 16:39 jast http://www.foswiki.org/Tasks/Item12936
  • jast no big changes there, really
  • 16:40 jast George will have to decide whether he's finished with that one
  • JulianLevens OK, so we leave as-is
  • 16:41 JulianLevens Then we have the catch-all for 1.2 doc updates which we leave as-is
  • 16:42 JulianLevens Now it seems to me that we have now covered the first item on the Agenda
  • jast nope
  • jast we can skip over all 'closed' tasks, but then there's 'confirmed' and 'waiting for' etc. further down the list
  • <- andreli has disconnected (Quit: Page closed)
  • JulianLevens ois
  • JulianLevens oic
  • 16:43 jast reading "Confirmed" as "this is an issue but nobody wants to tackle it"
  • 16:44 CDot suggest that as we are now well over finish time, we pat ourselves on the back and say "well done"?
  • jast +1
  • JulianLevens +1
  • 16:45 JulianLevens We meet again in two weeks I believe at 1300Z again
  • jast thanks, everyone
  • 16:46 jast can someone copy/paste the IRC log into the meeting topic?
  • JulianLevens Will do
  • jast that'd be rather clunky in my client, plus technically I missed the beginning
  • jast great
  • 16:47 JulianLevens jast: As you're doing the minutes, can you also update the tasks with state changes?
  • jast the minutes are already done
  • JulianLevens Superstar!
  • jast I'm washing my hands of all the rest
  • 16:48 jast kidding. I'll do it later though.
  • JulianLevens Thanks very much, and everyone else, see you again soon
  • ModAcOst cu
  • JulianLevens gac410: and now back to you

Topic revision: r11 - 21 Jun 2014, GeorgeClark - This page was cached on 13 May 2020 - 14:55.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy