Build, Release, QA
------------------
*rt additions*
Bear added --testcase as a command line option.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008428.html

Bear updated rt to always run a localized string validation step first, only run once. It won't run for a single test or for a performance test, but will run for -u and -f.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008429.html

rt will run into errors when run with versions before Python 2.4: you may need to upgrade Python on your intel mac. Bear also fixed a problem with the localization test on cygwin.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008435.html

John proposed giving better error messages for problems with rt, and either make rt run with Chandler's python or eliminate non-obvious failures for stock pythons on target platforms. Bear created Bug 9573 to track John's suggestions.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008439.html

*rt and Tinderbox*
Bear gave specific information about how Tinderboxes use rt:
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008453.html

*Localization Freeze*
Brian Kirsch gave July 9th as the localization freeze date. Before July 9th, make localizable string changes in the python code. After July 9th, make string changes in po files. Any textual changes made in python code will be immediately backed out of SVN. (The freeze date allows people to work on localizations.)
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008450.html

Dev
---
*Timezone changes*
Andi created a branch to work on Bug 9508 (index failures after timezone change) and related problems. Changing the default timezone globally caused indexes with floating events to get out of order. Changes include: - All static accesses to ICUtzinfo were changed to use view.tzinfo (same API)
- A view now persists its default timezone.
- Floating timezone operations delegated to view.tzinfo
- If a view's timezone is changed, a callback is invoked with view and timezone as arguments: it needs to invoke reindexing code to make events float - UI view's default timezone is set to system timezone, can be overridden with --tz
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008432.html

Bryan asked two questions: (1) why does each view need its own timezone? (2) Will views fight over different timezones? An index per timezone? Andi explained that each view needs to have its own default timezone until it commits -- consequences of changing a timezone are not shared until refresh. Once a view is refreshed, it will end up with the same timezone as the other views.
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008434.html

*Quick entry restructuring*
Phil Jones explained that he's reworking quick entry code to make it easier to add commands and functionality. Possible approaches: 1) Refactor quick entry code into a separate parcel. Commands would be persistent items, installed in a well known location. New parcels create persistent command items. Quick entry code would iterate through available command items. 2) Use a standard dictionary in a well known location. Add new keys with callback function. Similar to (1) but commands are not persistent items. Phillip Eby responded with feedback on how one might implement both approaches (including similar examples and sample code). He recommended defining entry points (implementation of #2) or the approach of defining a specialized Item class for commands (implementation of #1).
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008449.html

Meetings, Announcements
-----------------------
Grant gave a link to Guido's summary about Python 3000 and Python 2.6:
http://www.artima.com/weblogs/viewpost.jsp?thread=208549

IRC testing session on desktop deletion and trash features.
http://chandlerproject.org/Projects/TrashAndDeletionTestSpec
http://lists.osafoundation.org/pipermail/chandler-dev/2007-June/008447.html
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to