[Chandler-dev] alpha3/alpha4 and priorities

[Sheila Mooney]

Just a reminder that first draft for most of Alpha4 specs are ready  
and you can find all these links in the table on the 0.7 planning  
page - along with the status.
http://wiki.osafoundation.org/bin/view/Projects/ZeroPointSevenPlanning

The ones applicable for Alpha4 are...
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ 
Dashboard-0.7.html
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ 
Stamping-0.7.html
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ 
Sharing-0.7.html
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ 
Search-0.7.html
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ 
Sidebar-0.7.html
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ 
MiniCalPreview-0.7.html

Email is the primary one that's missing and we are working on that  
right now.



On Jun 29, 2006, at 2:50 PM, Katie Capps Parlante wrote:

> Ok, so I should have sent this out earlier, but a few words about  
> priorities as we transition from alpha3 to alpha4...
>
> + A "dogfoodable" alpha3 with background sync is the highest priority.
>
> This means that fixing background sync bugs and fixing regressions  
> are the most important tasks. If you have these bugs, or can help  
> someone who does, that is a good way to spend your time. :)  
> Friday's IRC testing session is important to shake out more  
> background sync/merging bugs.
>
> + Shoring up functional and unit tests is a high priority. Fixing  
> test failures is always a high priority.
>
> A healthy testing framework and comprehensive suite of tests (unit  
> tests, functional tests, etc.) is important to us working  
> efficiently as a team. It allows us to to make significant  
> improvements and changes to the code base (like the wx tarball or  
> the background sync feature) without disrupting everyone on the  
> team. It prevents introducing regressions as we add new features.  
> If you don't have alpha3 bugs, spending a few cycles enabling  
> functional tests that aren't working is a good idea. Adding new  
> tests to go along with the new features is also important.
>
> + A first pass at "experimentally usable" dashboard and scheduling  
> is high priority in alpha4 (including all of the work that supports  
> this, like domain model, stamping, search, a bit of email, etc.)
> + Continuing to improve "dogfoodability" is high priority in alpha4  
> (including data migration, sharing improvements, etc.)
> + Improving performance is high priority in alpha4
>
> We'll likely branch soon (today? Heikki will give the go ahead). If  
> you don't have alpha3 bugs or tests to write, getting started on  
> alpha4 work is a good idea. This includes performance work if you  
> have bugs/tasks to chase down slow use cases or write performance  
> tests. Spending a bit of time on list discussions to unblock  
> someone else's work on alpha4 is also appreciated.
>
> Sheila's Alpha4 plan of record:
> http://wiki.osafoundation.org/bin/view/Projects/DetailedAlpha4Plan
>
> Cheers,
> Katie
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev