Version 0.2.0
    * Project restructurization done. The next components allocated:
        - Library, which manages event creation, remove and select. Provided by 
            libkimi package.
        - Interface, which gives user access to library capabilities. Provided 
            by kimi-hildon and kimi-console package.
        - Modules, which implement concrete event sources:
            -- Google Calendar module. Provided by libkimi-google-calendar package.
            -- Calendar Backend module. Provided by libkimi-calendar-backend package.
      At this stage the project is unstable. Only build and packaging is guaranteed.

    * Version is updated to 0.2 due to global changes.

    * Hildon interface is planned to be fully rewritten, so, current version provides
      only empty window. Use kimi-console to test library functionality.

    * Repository is published at http://gitorious.org/kimi.    

Version 0.1.5
    * Localization
    
    * Error reporting in GUI
    
    * GUI improvements: occurence input and new layout in Create/Edit event dialog
    
    * Bugfixes

Version 0.1.4
    * Remote Storage: Upload events to Google.

    * Event Manager: Reminder for periodic event.

    * GUI: User interface for download window.

    * GUI: Search by day.
    
    * Feature freeze

Version 0.1.3:

    * Remote Storage: Download events from Google. Save them in local database.

    * Event Manager: Set reminder are implemented.

    * Event Manager: Deleting events.

    * GUI: Search events by filter string.


Version 0.1.2:

    * Event Manager: Given event can be stored to the DB.
    
    * Event Select: functionality for event searching is implemented.
    
    * GUI: User can view and edit existing events and can create new events.
    
    * Testing framework by Vladimir Kovalev is integrated to the project.


Version 0.1.1:

    * Basic memory management functions of the Event Manager are implemented:
      event structures can be created and destroyed.

    * Event Data Access subsystem is implemented: we can make queries to the 
      database.
      
    * Basic functionality of the Event Data Select subsystem is implemented:
      the list of events can be queried for the given time period.
      
    * GUI: User can see planned events for the selected month and for the selected day.


Version 0.1.0:

    * The planned architecture is moved to the code in form of function 
      prototypes and dumb functions with commented out flow description.
