https://bugs.meego.com/show_bug.cgi?id=14972

pohly <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #4 from pohly <[email protected]> 2011-05-02 12:46:46 UTC ---
commit bfefdb9b098361af81c2dc9be295ef622675d49c
Author: Patrick Ohly <[email protected]>
Date:   Mon May 2 20:13:23 2011 +0800

    nightly testing: renamed ical20/itodo20/vcard30/text, removed vcard21 from
Evolution backend (BMC #14972)

    The distinction between vcard21 and vcard30 became mute in the Evolution
    backend a while ago. Both tests ended up using the vCard 3.0 Evolution
    tests data and the default uri for each server. This patch removes
    the vCard 2.1 special case.

    It also renames the tests and test data to reflect that they always
    were Evolution specific. The new naming convention, also applied
    to file, QtContacts, KCalExtended, XMLRPC, Maemo and Akonadi backends, is
    now <backend>_contact/event/task/memo, with eds/file/qt/kcal/maemo/kde
    as backend names.

    The reasoning is:
    - results in unique string (in particular no overlap with
      backend type names), easier to search for
    - underscore already used before (in contrast to hyphen)
    - no plural-s to keep the name shorter

    The Akonadi backend should be using its own test data instead of
    the Evolution ones.

--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords: 
Status: RESOLVED
Who: [email protected]
Assigned To: [email protected]
Target Build: 1.2
Flags: 
Changed: Status Resolution
--------

https://bugs.meego.com/show_bug.cgi?id=14972


-- 
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to