From: Hilmar L. <hl...@ne...> - 2009-12-04 21:42:11
|
As a follow-up to our teleconference, here are our decisions and action items for the next conference call on Thursday next week. 1) We are going to table priority 2 and 3 items for now, unless they take no more than 2-3 hours to address. 2) Everyone please fill in effort estimates for the tasks in the tables that you are assigned to. If the ability to do so depends on better understanding the requirements first, please write that in. 3) Based on estimates, priority order, and your fractional allocation to work on TreeBASE, please propose feasible target dates for those tasks you are assigned to. 4) Tasks in the table that do not have a tracker item# yet should receive one (or more, if they decompose into multiple tracker items). This should be done by the assignee(s), and the item# recorded in the table. As a reminder, at next week's Thu conference call we will want to pin down a target date for the first TB2 public release. This will also help organize and time the logistics tasks necessary along the way (such as announcements, server deployment, language on the TB1 website, etc). BTW once we've filled everything in I would like to move the table to the TreeBASE wiki (which is public). Since the motivation for not starting it there isn't to keep it private until then but rather ease of editing it, let me know if anyone would have a problem or concerns with the Google Doc being made public right away. -hilmar On Dec 3, 2009, at 10:55 AM, hl...@ne... wrote: > Hi all, > > here's an initial draft of a release planning and prioritization > document that we can use as a basis for our conference call. I > seeded it with the tasks that Val sent and added a few more. I also > put them into different categories to give us a sense of perspective > in which areas action is needed. > > -hilmar -- =========================================================== : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : =========================================================== |
From: Rutger V. <rut...@gm...> - 2009-12-07 11:14:15
|
> BTW once we've filled everything in I would like to move the table to > the TreeBASE wiki (which is public). Since the motivation for not > starting it there isn't to keep it private until then but rather ease > of editing it, let me know if anyone would have a problem or concerns > with the Google Doc being made public right away. Why the wiki? Can't we just stick them in the tracker with the understanding that the highest priority (9) means pre-release milestone? I'm worried about redundancy in where we put the TODO items and I feel that the wiki ought to consist of (develop/build/deploy/architecture) documentation, not time-sensitive, aspirational shopping lists. > On Dec 3, 2009, at 10:55 AM, hl...@ne... wrote: > >> Hi all, >> >> here's an initial draft of a release planning and prioritization >> document that we can use as a basis for our conference call. I >> seeded it with the tasks that Val sent and added a few more. I also >> put them into different categories to give us a sense of perspective >> in which areas action is needed. >> >> -hilmar > > -- > =========================================================== > : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : > =========================================================== > > > > > ------------------------------------------------------------------------------ > Join us December 9, 2009 for the Red Hat Virtual Experience, > a free event focused on virtualization and cloud computing. > Attend in-depth sessions from your desk. Your couch. Anywhere. > http://p.sf.net/sfu/redhat-sfdev2dev > _______________________________________________ > Treebase-devel mailing list > Tre...@li... > https://lists.sourceforge.net/lists/listinfo/treebase-devel > -- Dr. Rutger A. Vos School of Biological Sciences Philip Lyle Building, Level 4 University of Reading Reading RG6 6BX United Kingdom Tel: +44 (0) 118 378 7535 http://www.nexml.org http://rutgervos.blogspot.com |
From: Hilmar L. <hl...@ne...> - 2009-12-07 17:44:36
|
On Dec 7, 2009, at 6:14 AM, Rutger Vos wrote: >> BTW once we've filled everything in I would like to move the table to >> the TreeBASE wiki (which is public). Since the motivation for not >> starting it there isn't to keep it private until then but rather ease >> of editing it, let me know if anyone would have a problem or concerns >> with the Google Doc being made public right away. > > Why the wiki? Can't we just stick them in the tracker with the > understanding that the highest priority (9) means pre-release > milestone? An issue tracker is not the same thing as a release plan, so they are not redundant at all to me. The tracker adds a lot of stuff that's important for tracking issues, but clutter for a release plan. There are things about a release plan that have little to do with tracking resolution of issues. I don't share your concern that these could go out-of-sync. We are not going to track resolution in the release plan (except to update when something is complete), and if tasks get added to or removed from critical for release-status we need to be more explicit about that than updating the priority in the tracker (which will remain obscure to most on the stakeholder team). -hilmar -- =========================================================== : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : =========================================================== |