[Chandler-dev] [QA] testing the background-sync branch

[Katie Capps Parlante]

Hi Morgen,

I tried out the bgsync branch last Friday, sharing calendars between an 
instance on my xp desktop and an instance on my mac laptop. After 
getting past one bug (which Andi fixed quickly), it seemed pretty 
stable. I didn't test recurrence or stamping.

Given that making this work is very high priority for alpha3, I think we 
need to take a few next steps:

+ develop a test plan with qa and get qa started on testing
+ get other people using it/testing it
+ find a way to automate testing (unit tests and/or functional tests)

I think it is a good idea to start testing now, to give us time to deal 
with problems and make sure the schedule is realistic. We can either do 
this by testing the branch or by going ahead and merging the branch 
changes to the trunk.

Thoughts?

Cheers,
Katie

Morgen Sagen wrote:
> The 'bgsync' branch is at the point where brave souls can start trying 
> it out.  We don't have downloadable distributions of it, but you can 
> just check out the branch via:
> 
>    svn co http://svn.osafoundation.org/chandler/branches/bgsync/
> 
> Then cd to the bgsync directory and 'make install' to get the binaries.  
> If you find bugs that don't happen on the trunk but happen on bgsync, go 
> ahead and file them against me (along with the steps to reproduce them) 
> for triage.
> 
> Some notes about what you should try (and not try) to test are at:
> 
>    http://wiki.osafoundation.org/bin/view/Journal/SharingTests
> 
> I expect once we have the last remaining issues worked out, we can land 
> these changes on the trunk at the beginning of the alpha3 phase.
> 
> Thanks,
> ~morgen
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> 
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev