| [cosmos-dev] RE: ER 216529 - is http://wiki.eclipse.org/COSMOS_QA_i9_Activities#In_scope_i9_ERs correct? |
Ruth, Thanks for confirming that we are on the same page... Also, in this page, I do mention that all the build ERs will not be in place for i9. That said, the sub-team leads will execute stop gap processed in i9 to address the gaps due to some of the build ERs being pushed to i10. This is also documented in http://wiki.eclipse.org/COSMOS_QA_i9_Activities.... The point is to ensure that QA does not end being responsible for any tasks due to missing Junits, and we upfront the build issues prior to the code complete date (Feb 22). The primary vehicle for the latter will be the weekly integration builds and the testing done on these be Development.... Your point about QA testing on additional platforms is captured as an issue on the http://wiki.eclipse.org/COSMOS_QA_i9_Activities page. I defer this one to Kishore / Srinivas. Thanks, Jimmy ________________________________ From: cosmos-dev-bounces@xxxxxxxxxxx on behalf of Ruth Lee Sent: Thu 1/31/2008 11:57 PM To: Cosmos Dev Cc: Doma, Srinivas Reddy; Adivishnu, Kishore Subject: Re: [cosmos-dev] RE: ER 216529-is http://wiki.eclipse.org/COSMOS_QA_i9_Activities#In_scope_i9_ERscorrect? Your summary matches my understanding of what we discussed in the Community call today. I like DW's suggestion where QA could be asked to step in and help out with running JUnits on additional platforms. However, looking at Tania's list, the build features on the list for i9 do not match what we discussed in the build/RE meeting last week. I understand that Tania will be out tomorrow so I'll sync up with her on Monday to figure this out. The build features in the i9 list are as follows: P2 215135 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=215135> Establish a process for running JUnits against a COSMOS build Project/Process Balan Subramanian P2 216210 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=216210> Define COSMOS 1.0 hardware & software operational guidelines, recommendations, and best practices RE Balan Subramanian P2 216211 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=216211> We need an ongoing Build process to facilitate a continuous test loop RE Balan Subramanian P2 216591 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=216591> build "fire alarm" notification email RE Balan Subramanian And from Tania's earlier email, this is what we decided were the most important in last week's call (not listed in implementation order): 1. Establish a process for running JUnits against a COSMOS build - 215135 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=215135> 2. Enable anyone to run COSMOS build (move build to Eclipse server, complete build documentation) - 206374 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=206374> , 216499 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=216499> , 216211 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=216211> 3. Send notifications of problems with daily builds (build breaks, missing copyrights and about.html files, etc.) - 210263 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=210263> 4. Refactor Packaging - 216169 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=216169> Ruth Lee IBM Toronto Lab ruthdaly@xxxxxxxxxx T/L 313-4453 "Mohsin, Jimmy" <Jimmy.Mohsin@xxxxxx> Sent by: cosmos-dev-bounces@xxxxxxxxxxx 01/31/2008 03:09 PM Please respond to Cosmos Dev <cosmos-dev@xxxxxxxxxxx> To "Cosmos Dev" <cosmos-dev@xxxxxxxxxxx> cc "Doma, Srinivas Reddy" <SrinivasReddy.Doma@xxxxxx>, "Adivishnu, Kishore" <Kishore.Adivishnu@xxxxxx> Subject [cosmos-dev] RE: ER 216529 -is http://wiki.eclipse.org/COSMOS_QA_i9_Activities#In_scope_i9_ERscorrect? Hi David / Tania, Agreed, will point to the master list. Thanks for prompt reviews / input Ruth / Team, Any input from you end? Thanks, Jimmy "Daddy" Mohsin Cell +1-609-635-1703 From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Tania N Makins Sent: Thursday, January 31, 2008 3:04 PM To: Cosmos Dev Cc: Doma, Srinivas Reddy; Adivishnu, Kishore Subject: Re: [cosmos-dev] ER 216529 -is http://wiki.eclipse.org/COSMOS_QA_i9_Activities#In_scope_i9_ERscorrect? Jimmy, I added enhancement 217301 and removed 215534 from this table. I have been trying to keep a master list here: http://wiki.eclipse.org/Cosmos1.0Features. Any reason why the QA document can't just point to the master table to avoid updating multiple pages? Tania 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 "Mohsin, Jimmy" <Jimmy.Mohsin@xxxxxx> Sent by: cosmos-dev-bounces@xxxxxxxxxxx 01/31/2008 02:02 PM Please respond to Cosmos Dev <cosmos-dev@xxxxxxxxxxx> To "Cosmos Dev" <cosmos-dev@xxxxxxxxxxx> cc "Doma, Srinivas Reddy" <SrinivasReddy.Doma@xxxxxx>, "Adivishnu, Kishore" <Kishore.Adivishnu@xxxxxx> Subject [cosmos-dev] ER 216529 - is http://wiki.eclipse.org/COSMOS_QA_i9_Activities#In_scope_i9_ERs correct? Tania, Can you please confirm that the table in the section http://wiki.eclipse.org/COSMOS_QA_i9_Activities#In_scope_i9_ERs <http://wiki.eclipse.org/COSMOS_QA_i9_Activities#In_scope_i9_ERs> is correct? This section lists all the i9 ERs that are in scope for QA. Kishore, Please note that there is a link to a Bugzilla query at the top of this section; you can ensure that the table is in sync with Bugzilla by clicking on the query link. That said, if Tania confirms that the table is correct and there are not more i9 ERs coming, you may not even need to run the query.... Thanks, Jimmy Mohsin Cell +1-609-635-1703 _______________________________________________ cosmos-dev mailing list cosmos-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cosmos-dev_______________________________________________ cosmos-dev mailing list cosmos-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cosmos-dev
<<winmail.dat>>