http://bugs.meego.com/show_bug.cgi?id=8684
Summary: nightly testing: MeeGo chroot
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: major
Priority: Undecided
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
We should include testing on MeeGo to our nightly testing. The goals are:
* catch build errors which only occur with MeeGo configure options
(--enable-kcalextended --enable-qtcontacts) and/or the libs/compiler
in MeeGo
* local testing of these two backends and the underlying storage
* reference platform for Buteo testing
Yongsheng, Qiankun, can you take on that task?
We need multiple MeeGo chroots:
* 1.1
* Trunk
Updating Trunk should be done so that
a) a snapshot is taken (cp -a --link)
b) update
c) run sanity checks (SyncEvolution Source::Local?)
d) if these fail, fall back to snapshot
Nightly testing should include information about the last update made on each
chroot. ("Trunk 2010-10-20").
--
Configure bugmail: http://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
