Current Combined Status
This page consolidates the status of all the different projects.
Plans for 0.3.24 Integration Point B
Plans for 0.3.25 Feature Freeze
Planning to not do in .4
Reviews
- Morgen's sharing ui code (Morgen to schedule)
- Katie's calendar/collection canvas (Katie to schedule)
- Donn's notification to main view (Donn to schedule)
- John (and others) attribute editor/renderer (not ready yet)
- mail content model (wait for Brian to get back)
Issues
- Short term owner for mail bugs?
- Content model for sharing
- Will item collection fixes be accepted?
- Team would like clarity on how bugzilla will be used in release process (which fields are relevant)
- Would be good to have a follow up meeting on sharing (Sheila to schedule)
Plan for milestone 0.3.25
- Build: Milestone build next week will be delayed from Sept 21 to Sept 22 or 23.
- Build: wxWidgets version upgrade is on a separate branch to minimize effect on other stuff
- Build: Heikki plans to fix Linux launcher bug and a similar bug for Windows that has a nasty workaround.
- QA: Aparna to work on script for demos as well as regular bug finding and resolution.
- Stuart: Fix a couple bugs, improve sharing unit tests
- Stuart: Code review already done
- Brian: code reviews when he gets back
Bugzilla status by person (shows only tasks that have been entered in Bugzilla):
Plan 3.24 [9/7]
- Persistence: Version merging
- Queries: evaluation engine, use existing repository storage structures (indices?)
0.4 Community Goals
- One or two people helping with QA for the repository -- confirming bugs, reducing test cases, etc.
- One or two people working on the repository.
- Not originally a goal, but spin out pylucene project and add contributers
Plan for 0.4 (3.25) [9/21]
By Integration Point "B"
- Complete first draft of production projects for following:
- Rule builder
- Dashboard view
- Universal text entry box
- Brainstorm and scope search
- Conduct lightweight (concept and paper prototype) usability tests
0.4 (Projects.ZeroPointFour?) Goals
- wxWidgets 2.5 migration - completed
- Dependencies don't work in all cases; fix them: (30 Apr) Medium
- Investigate switching away from CVS (Subversion, Perforce, ...): (21 May) Medium/Large
- Would obviously affect Bonsai, LXR, maybe other webtools
- Keep up to date with latest releases of 3rd party libraries: ongoing
- Try to reduce Chandler's dependancy of slightly modified 3rd party libs - try to get Chandler use the standard libs: (21 May) Medium/Large
- Automate more of the build and release process
- Smarter Tinderbox (performance reporting, separate release and debug builds, Bonsai links, ...): (28 May) Medium/Large
- Automatic checksums on download packages: - completed
- Keep Tinderbox in green - goal is to have outages last less than 6 hours at a time.
- And in general managing build & release bug list
- See also Projects.ReleaseEngineeringGoals20040309 meeting notes.
- Community-related goals:
- one or two more ports.
- Rationale: this helps verify we're not doing things that make porting hard. It also allows developers using othe distributions to participate.
- Steps to encourage: Have a list of past and existing ports. Have easy to find info on wht to do if one needs help.
- volunteers setting up more tinderboxes running on their machines that would report to our tinderbox which would display the results along with our tinderboxes.
- Rationale: This allows us to see run thorough build cycles with more options -- release and debug builds, some different options on each, and for each platform.
- Steps to encourage: get our infrastucture ready to accept data from other tinderboxes, and hopefully make it easy to add tinderboxes. Create a good set of information about why this is valuable, how to set up a tinderbox, how to send the data to us.
- evaluate build-related feedback from Projects.PyCon and determine if there are easier or standardized ways that we should incorporate.
- find one or two people with lots of python build experience to make suggestions about build improvements
Plans for 0.4 Integration Point A
| Goal | Status |
|---|
| Prepare presentation and demo for OSCON 2004 | done |
Plans for Milestone 0.3.21
Plans for 0.4 Integration Point B
Plans for 0.4 Release
| Goal | Status |
|---|
| Prepare presentation and demo for Web 2 conference | not started |
| Prepare presentation and demo for EDUCAUSE 2004 | not started |
Cross-project status
Projects.EngineeringIssues doesn't yet have status by milestones, but might someday.
We don't have a good status page for IT, but see
Trash.EngineeringRequestsForIT.
--
Projects.DuckySherwood - 06 Jul 2004
