The expire date has been extended to June 1.
	The "To Do List" text field has been replaced by a pop-up list that allows you to filter the to-do items which are displayed.  The list contains an entry for each of your roles.  If one of the roles in the list is selected, only those to-do items which belong to that role will be displayed.  The list also contains two special entries:

		"All To-Do's" displays all to-do items, with no filtering.
		"Selection To-Do's" displays only those to-do items that belong to the currently selected role or goal in the browser.  The items displayed change when the browser's selection changes.

See the section titled "To-do lists" for more information.

	A "Weeks" unit has been added to the reminder inspector, so you can now specify reminder times in minutes, hours, days, or weeks.
	A panel is now displayed whenever all appointments need to be loaded.  Previously, Chronographer only displayed a busy cursor during loading.  There are three occasions when all appointments must be loaded:  copies or cuts of roles, goals, or tasks; merges of tasks; and during some upgrades to fix the possible effects of bugs.
	The Mailing List... command now initializes the email address field to the ReplyTo preference from Mail.app, if it's been set. The command will also now attempt to verify that the address entered contains a domain name.
	If you used this command to join the list but didn't get a reply, it was probably because you didn't specify a domain name in your address.  I've received several requests to join the list from addresses with no domains, and I had no way to correct them or contact the people who sent them, since there was no domain given.  Please try again using a domain name.
	The Calendar window now stays visible when Chronographer is deactivated.
	The clock icon now appears immediately after Chronographer is launched.  Previously it only appeared after Chronographer had finished initializing.
	The expire warnings will now only occur once each at seven, three, two, and one days before the expire date.  Previously, an expire warning would occur every time Chronographer was launched within seven days before the expire date.
	Chronographer will now expire exactly at midnight on the expire date.  If it is running at that time, it will open a panel saying that it has expired and will then exit.  Previously, Chronographer would only check for its expiration when it was launched, so people who stay logged in all the time could evade the expiration.  Of course, this may not be considered a feature by some.  :)

Bugs fixed:

	Under certain circumstances, Chronographer would enter an infinite loop after presenting a reminder for a non-repeating item. Unfortunately, the next time Chronographer was started, it would issue the same reminder and go into the same infinite loop.  I only received one report of this bug, but it could've potentially affected many users.
	When the new version of Chronographer first runs, it will load all of your appointments to fix appointments which have errors in their "end times" which provoke this bug.  No there is no risk of data loss or corruption.
	Merges of more than two items only merged the odd items in the selection.
	Merges of roles did not remove the merged roles from the browser, even though they were deleted, and selecting one of those deleted roles would crash Chronographer.
	Deleting an item while it was being edited in the inspector panel sometimes caused Chronographer to crash.
	Sometimes when an appointment was dragged into a schedule window, the schedule was scrolled immediately to the very top or very bottom.  Thank God this very annoying bug is now history.
	The "Now" button would select yesterday instead of today if the "Last hour" preference was set to 24:00 instead of 0:00.
	When an role or goal's name was changed (via the inspector), the inspector changed to "No Selection" even though the item was still selected.
	Autobumps and time summary period updates did not take advantage of the new alarm system that the reminders now use to stay in sync with the system clock.  They do now, so they will occur exactly on time, even if daylight savings time changes while Chronographer is running.