Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[hyades-dev] Commiter call minutes Oct 25


Attending
Nellie Chau, Richard Duggan, Eugene Chan, Joe Toomey, Kent Siefkes,  Dave Mercer for Antony, Sri Doddapaneni, Harm Sluiman

Absent
Antony, Rob

3.0.1.1
- no new activity, down stream products are still pending closure so we believe we are done, but are monitoring final acceptance from downstream products.
3.0.2
- branch will be created this week and approval and build process will begin at the next commiter call.
3.1
- complete and no activity
3.2
with less than 1 week left for coding of iteration 1 but a large number of outstanding targeted features and enhancements are still open. The following is the commiter level assessment
i1
Nellie - features and defects on track
Richard - features on track but 8  out of 20 defects will be re-targeted for i2.
Eugene -features on track but 20 out of 50 defects will be re-targeted for i2.
Joe - 1 feature being re-targeted for i2 and defects on track
Kent - concern about one feature and will resolve with Marius, most defects are i2 targeted
Antony - on track

i2
Nellie - features and defects on track
Richard - Need reassessment but not expecting a major problem to contain.
Eugene - expect to be ok because work was front loaded to i1.
Joe - on track, but is short on planned resource
Kent - on track
Antony - on track

un-targeted
all are assumed to be re-targeted to future or 3.3 and this was confirmed. Clean up will occur shortly

This suggests that 3.2 is going to be on track in the end but we need to pay attention to the defect backlog as it is not coming down as quickly as intended. The objective for defects was to get the backlog closed primarily during 3.2 with some final defect cleanup in 3.3. Now we are looking at a significant effort through to the end of 3.3.


component/project matrix:
Harm remade the request for plugin mapping to the project/component matrix and commiters per plugin. This input is critical to get closure on the commiter matrix and component ownership by project. The intent is to begin working the 3.2 i2 activities with the new structure in mind so that the system will be ready as 3.3 work starts in the new year.

We reviewed the requirements process:
Anyone can submit new requirements/enhancements via bugzilla. They will remain un-targeted and un-prioritized until they pass through the requirements and planning process, at which time the bugzilla entry will be updated to reflect the commitments for the enhancement. Bugzilla will be used to track the development effort along with the defect and other activities in the overall project. While the features are being assessed and approved they will be periodically published on the website to reflect the accurate approval state. The web site content will be where the requirements and planning group publish approvals and activity in this area of the process.
From a bugzilla and workflow perspective this is the same as how defects are managed other than defects are approved and assigned by the commiters directly.

maintenance stream request process:
Kent raised the question about how consuming products can request maintenance streams such as 3.0.1.2, and how responsive would TPTP be. The answer is that the consumer needs to make the request to the PMC or project where it will be assessed as quickly as possible, To date there has only been one main consumer pushing fix releases, but the PMC will be responsive to all requesting consumers. All possible efforts will be made to match the responsive needs of the consumer. We definitely want to discourage the consumer of patching drivers themselves due to the complications of update manager over writing scenarios.

Thanks for your time.
--------------------------------------------------------------------------
Harm Sluiman, STSM,  
phone:905-413-4032   fax: 4920  
cell: 416-432-9754
mailto:sluiman@xxxxxxxxxx
Admin : Gabrielle Chapman chapmaga@xxxxxxxxxx  Tie: 969-2323

Back to the top