Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cosmos-dev] REVIEW REQUESTED TODAY: Code Cutoff for WeeklyIntegration Builds
+1 overall.
 
I agree with Ali's comment that we need clarity on who will run what and where we will post the results but I suspect that we will need to discuss the specifics of the proposal to finalize a plan.
 
The only quibbles that I see with Tania's proposal are that we describe both the Tuesday and Wednesday builds as "integration builds" and David's comment about not needing to run the tests individually because we don't intend to post the results - not check them in to CVS.
 
Don



The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Ali Mehregani
Sent: Thursday, February 14, 2008 3:36 PM
To: Cosmos Dev
Subject: Re: [cosmos-dev] REVIEW REQUESTED TODAY: Code Cutoff for WeeklyIntegration Builds

+1 (as long as cvs lock down is limited to 1 hr)
Here's a suggestion: along with each integration build we can have a wiki template that outlines components of subprojects that need to be tested.  Whoever that runs the test can indicate the pass rate (think of it as a check-list).  For example:

Resource Modeling
  • CMDBf query/registration APIs - assignee: Ali Mehregani  (result: 87% pass)
  • SML repository APIs - assignee: Ali Mehregani (result: 90% pass)
  • ...
Data Collection
  • Broker/Management Domain APIs - assignee: ...  (result: ___)
  • Data Manager APIs - assignee: ... (result: ___)
....

A consistent template for each integration build provides clarity on who is testing what.


2008/2/14 Tania N Makins <tmakins@xxxxxxxxxx>:

Team,

Please review the process changes related to code cutoff for the weekly integration builds below and respond with comments or a +1 if you are in agreement by EOD today.  

Weekly Integration Builds

  • Weekly integration builds will be run every Tuesday at 12:00 p.m. ET
  • Code cutoff for integration builds is as follows:
    • All patches should be in bugzilla by Monday at 12:00 p.m. ET
    • All code should be checked into CVS by 11:45 a.m. ET on Tuesday
    • CVS will be locked until the build has completed successfully (typically for 1 hour).  No code should be checked in from 11:45 a.m. on Tuesday until notification of build completion has been sent out.
    • Each subproject team should run JUnits on the candidate build and post results by 10:00 a.m. on Wednesday to be reviewed during the architecture call. JUnits should be run individually so that results can be reported accurately. (Note: The Data Visualization team will perform a smoke test on the UI since the tests are manual)
    • RE team will post notification to cosmos-dev when the integration build is ready - target availability is 4:00 p.m. on Wednesdays



        Tania N. Makins, PMP®
        Project Manager, AC Open Source Components
        IBM Software Group - RTP, NC
        Office: (919) 254-8430  T/L: 444-8430
        tmakins@xxxxxxxxxx

_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev




--
Ali Mehregani
COSMOS Project
http://www.eclipse.org/cosmos/

Back to the top