--- Comment #1 from yongsheng <yongsheng.zhu(a)intel.com> 2010-10-20 01:40:41 PDT ---
(In reply to comment #0)
We should include testing on MeeGo to our nightly testing. The goals
* catch build errors which only occur with MeeGo configure options
(--enable-kcalextended --enable-qtcontacts) and/or the libs/compiler
* local testing of these two backends and the underlying storage
* reference platform for Buteo testing
Yongsheng, Qiankun, can you take on that task?
yes, we should add testing for these
We need multiple MeeGo chroots:
Updating Trunk should be done so that
a) a snapshot is taken (cp -a --link)
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").
I think we can postpone it since our schedule is tight.
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.