I wanted to summarize a couple of process decisions we've made recently
about back-end server, web UI and web widget work...
* We're tracking tasks for the above in one prioritized queue:
http://chandlerproject.org/Planning/WebWorkQueue
- If a bug in the queue is "ASSIGNED", it means that a developer is
currently working on it.
- If a bug in the queue is "NEW", it is up for grabs.
- Devs will take bugs based on the highest priority "NEW" bugs that fit
their skill sets.
- Bugs have been prioritized by ppd, with some adjustments made by devs
based on dependencies, etc.
- This queue contains all "1.0" bugs (a conservative list). Other
buckets are "1.0 candidate" and "Future".
- As new bugs get logged, Sheila will triage them into this queue or
into the other buckets. Speak up on this list if you object to Sheila's
initial triage of any particular bug.
* After two Cosmo releases this month, the plan is to do server releases
(and corresponding Hub upgrades) once a month.
- 0.13 will be a security release, taking in Randy's recent work
plugging a security hole (also picking up a few other bug fixes).
- 0.14 will be an infrastructure release, upgrading to Dojo 1.0
- We'll move to monthly releases, pulling any items from the queue that
have been completed.
- We'll launch web widgets as they are completed (or at least completed
enough to be usable).
* We'll cut a 1.0 release once we've hit all the required work items
from the queue.
- Web widgets don't all need to be completed for a 1.0 server release.
- We'll probably need some extra QA work for the 1.0 release.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
