Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "DSDP/TM/Committer Phone Meeting 21-Aug-2007"

< DSDP‎ | TM
Line 24: Line 24:
  
 
=== Current Work ===
 
=== Current Work ===
* {{Bug|200557}} - DaveM: Review dnd from Project Explorer ({{Bug|192704}}
+
* '''Reminder: Aug 30th is RC1''' as per [[TM 2.0 Ramp down Plan for Europa#Ramp_down_for_Europa_SR1_.2828-Sep-2007.29]], no risky fixes for 2.0.1 after the 30th! (Will fork off a 2.0.1 branch by then)
* {{Bug|199565}}, {{Bug|199566}}, {{Bug|199568}} - DaveM: Deadlock issues due to synchronized methods calling out
+
* '''Reminder: Start preparing / planning''' for the [[DSDP/TM/Face-to-face Meeting Toronto 17-Sep-2007]]
* {{Bug|168219}} - Kevin: how to treat recursive delete of a tree where some elements are read-only
+
* '''DaveD:''' {{Bug|194802}} - NPE when restoring; might be gone in the meantime, analyze / reproduce?
 +
** {{Bug|198395}} - Connect dstore with expired password
 +
** {{Bug|197036}} - Avoid plugin activation, dont create all filterpools on startup
 +
* '''DaveM:''' {{Bug|196662}} - Refresh queries on dispatch thread - is it all fixed now?
 +
** {{Bug|200557}} - Review dnd from Project Explorer ({{Bug|192704}}
 +
** {{Bug|199565}}, {{Bug|199566}}, {{Bug|199568}} - Deadlock issues due to synchronized methods calling out
 +
* '''Kevin:''' {{Bug|168219}} - how to treat recursive delete of a tree where some elements are read-only
 
** Looks like we'll need additional API in IFileService#delete() to ask "force" (delete read-only elements by setting them writable before deletion). That API might also go into EFS
 
** Looks like we'll need additional API in IFileService#delete() to ask "force" (delete read-only elements by setting them writable before deletion). That API might also go into EFS
 
** Or, we return errors as a MultiStatus, and allow setting all read-only elements writable right from the table in the confirmation dialog (EFS does not do that)
 
** Or, we return errors as a MultiStatus, and allow setting all read-only elements writable right from the table in the confirmation dialog (EFS does not do that)

Revision as of 08:17, 21 August 2007

Meeting Title: TM Committer Phone Meeting
Date & Time: Tuesday Aug 14, 2007 at 1500 UTC / 1100 Eastern
Dial-in: International +44 (0)1452 567588 / Freephone +1 (866) 6161738 / UK 08712460713
Passcode: 0587322148 #

MartinO to start conference call - please dial in using the numbers above.
Please be available for Skype Chat in parallel to the call. MartinO will start Skype chat just prior to call.
Skype fallback dial-in - only if less than 5 participants: martin.oberhuber, ddykstal (or david_dykstal), david-k-mcknight, kushal.munir, kevin.j.doyle, xuan.chen886, javier.montalvoorus, tedatteddotnet, michael_scharf, and uwe.stieber.

Attendees

  • IBM - Xuan Chen, Kevin Doyle, Dave Dykstal, Dave McKnight
  • Wind River - Martin Oberhuber

This is an Open call, so anyone else can join (though we expect the talk to be interesting for committers only).

Agenda

Current Work

  • Reminder: Aug 30th is RC1 as per TM 2.0 Ramp down Plan for Europa#Ramp_down_for_Europa_SR1_.2828-Sep-2007.29, no risky fixes for 2.0.1 after the 30th! (Will fork off a 2.0.1 branch by then)
  • Reminder: Start preparing / planning for the DSDP/TM/Face-to-face Meeting Toronto 17-Sep-2007
  • DaveD: bug 194802 - NPE when restoring; might be gone in the meantime, analyze / reproduce?
    • bug 198395 - Connect dstore with expired password
    • bug 197036 - Avoid plugin activation, dont create all filterpools on startup
  • DaveM: bug 196662 - Refresh queries on dispatch thread - is it all fixed now?
  • Kevin: bug 168219 - how to treat recursive delete of a tree where some elements are read-only
    • Looks like we'll need additional API in IFileService#delete() to ask "force" (delete read-only elements by setting them writable before deletion). That API might also go into EFS
    • Or, we return errors as a MultiStatus, and allow setting all read-only elements writable right from the table in the confirmation dialog (EFS does not do that)
    • Users will want recursive-delete including deleting read-only files. What's the best UI to give it to them?
      • Search for read-only-files, set writable, then delete
      • Do it all-in-one?
  • BugDayAugust2007 -- August 31 -- TM taking part: committers sign up if they can hang out on IRC, add "bugday" keyword to applicable bugs
  • Questions


Vacation, Away

  • Xuan week off end of August
  • DaveD vacation Aug.8 till Aug.20
  • DaveM vacation Aug.6 till Aug.21
  • Javier vacation Aug.13 till Aug.31

Action Items

  • Last Meeting Action Items
  • DaveD: 2.0.1 important fixes, then Doc bugs (Tutorial)
  • DaveM: Ask Pete Nicholls about room for F2F meeting in Toronto; bug 196662 refresh on dispatch thread
  • Xuan: Unit Tests
  • Kevin: 2.0.1 fixes
  • Martin: Look at PropertyDescriptor issues; EFS fixes; unit tests; Migration Docs, EFS Fixes, Releng Fixes, Newsgroup
  • Javier: 2.0.1 fixes, unit tests
  • Michael: Terminal performance improvements

Next Meeting

Back to the top