From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Tania N Makins
Sent: 15 February 2008 16:28
To: Cosmos Dev
Subject: RE: [cosmos-dev] REVIEW
REQUESTED TODAY: Code Cutofffor WeeklyIntegration Builds
Team,
Thank
you for the quick response on this proposal. I have tried to address most
of the comments posted by revising the weekly integration and iteration test
pass processes. Please review the proposed revisions below and post a +1
or any additional comments you have.
There
were 2 comments posted that are not addressed in these processes:
- I think Ali's suggestion
should be discussed at a subproject team level. Each subproject team
should determine which tests need to be run, who should run them, and how
they track results. One representative from the team should be
responsible for reporting status on behalf of the team.
- Don raised a point about a
reference to integration builds on both Tuesday and Wednesdays. The
intent is for Tuesday to be the day for code cutoff and build kickoff, and
for Wednesday to be the day the stable build is declared. If that is
not clear in the process document, please provide a suggestion for
rewording.
Note: Since we had declared code
cutoff for i9 to be Wednesday, February 20, I would like to propose that only
for i9 we move the final integration build code cutoff to Wednesday at 11:45
a.m. For i10 and i11, we can adjust the schedule to align with the
Tuesday integration build schedule. Thoughts?
Revised
Processes
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. (Note: The Data Visualization team will perform a smoke
test on the UI since the tests are manual. Also, the use of TPTP for
generating reports is not required for weekly integration builds.)
- RE team will post
notification to cosmos-dev when the integration build is ready - target
availability is 4:00 p.m. on Wednesdays
Iterations
4. Complete Test
Pass
- During the iteration test
phase, the code base is frozen.
- Only fixes for problems
found during testing should be checked in during the test pass. All code
must be reviewed and approved before checking in. Developers should post
request for approval in the bugzilla entry and post a note to the
cosmos-mgmt mailing list detailing the changes that need to be checked
in, the reason this change is critical for the current iteration and the
risk associated with introducing this change in the build. The Release Engineering
team will be notified of any approved fixes.
- Each subproject should
run the appropriate JUnit or manual tests. JUnits should be run
individually so that results can be reported accurately.
- Once a subproject team
determines that the test has completed successfully, the team lead should
post a message to the dev mailing list indicating that the JUnit or
manual tests for the subproject have been completed.
- Once all subprojects have
confirmed successful completion of the test, the release engineering team
will declare a candidate build and the QA team will be notified to begin QA
test activities.
- The QA team will open
bugs for any problems found during their testing activities and post
daily progress reports. If a fix is approved for check-in, the
Release Engineering team will declare a new candidate build which
includes the fix.
- Once the QA team
completes their testing activities, they will post a final test pass
report and the COSMOS PMC will begin evaluation of the iteration exit
criteria.
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
|
"Ebright, Don"
<Don.Ebright@xxxxxxxxxxxxx>
Sent
by: cosmos-dev-bounces@xxxxxxxxxxx
02/15/2008 07:44 AM
|
Please
respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>
|
|
|
To
|
"Cosmos Dev"
<cosmos-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
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/ _______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
