Bugzilla – Full Text Bug Listing
| Summary: | Communicate | ||
|---|---|---|---|
| Product: | [Modeling] MDT | Reporter: | Anne Jacko <anne.jacko> |
| Component: | Releng | Assignee: | Dummy mdt releng inbox <mdt-releng-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | alexander.igdalov, borlander, bruck.james, davidms, give.a.damus, Kenn.Hussey |
| Version: | unspecified | Flags: | Kenn.Hussey:
galileo+
|
| Target Milestone: | M4 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 252789 | ||
|
Description
Anne Jacko
Component leads, please add a comment to this bug that 1) confirms you are watching "cross-project.inbox@eclipse.org" and 2) lists the communication channels available for the individual responsible for your builds. Once this has been done for each component on the train, I'll resolve this bug. Confirmed. Confirmed for UML2 (In reply to comment #2) > Confirmed. > Thanks, Ed. You still need to list the communication channels available for the person who is responsible for XSD builds. (In reply to comment #3) > Confirmed for UML2 > Thanks, James. You still need to list the communication channels available for the person who is responsible for UML2 builds. Confirmed for OCL (assuming that Nick's contact info is known) Nick is helping. My e-mail works when he's not available. (In reply to comment #6) > Confirmed for OCL (assuming that Nick's contact info is known) OK, so on learning that Nick is not the build prime for the Modeling Project, I will be the OCL prime. E-mail and IM contact info: http://wiki.eclipse.org/User:Cdamus.zeligsoft.com (In reply to comment #8) > (In reply to comment #6) > > Confirmed for OCL (assuming that Nick's contact info is known) > > OK, so on learning that Nick is not the build prime for the Modeling Project, I > will be the OCL prime. > E-mail and IM contact info: http://wiki.eclipse.org/User:Cdamus.zeligsoft.com > Thanks, Christian. The release engineering strategy we are using for MDT is that each component lead is responsible for ensuring that their builds take place, that that contain the correct content, and are included on the train. Nick is responsible for the infrastructure that we're using and so will be considered a back-up contact. (In reply to comment #9) > > Thanks, Christian. The release engineering strategy we are using for MDT is > that each component lead is responsible for ensuring that their builds take > place, that that contain the correct content, and are included on the train. > Nick is responsible for the infrastructure that we're using and so will be > considered a back-up contact. Ah, I see. Of course, that makes perfect sense. I wouldn't expect anybody else to publish or verify the OCL builds, but when I have trouble producing a build, I'm generally as helpless as Bambi. :-) (In reply to comment #5) > (In reply to comment #3) > > Confirmed for UML2 > > > Thanks, James. You still need to list the communication channels available for > the person who is responsible for UML2 builds. Person responsible for UML2 build: jbruck@ca.ibm.com Back up: Nick. UML2Tools: 1) I am watching the cross-project.inbox@eclipse.org in Bugzilla 2) I am also the person responsible for U2T builds: michael.golubev@borland.com; borlander@gmail.com, YM: mgolubev_spb_ru. I listed myself (davidms@ca.ibm.com) as build lead for EMF, so given the combined build, that also makes me build lead for XSD. Nick is also my backup. SBVR will not be on the train. (In reply to comment #1) > Component leads, please add a comment to this bug that 1) confirms you are > watching "cross-project.inbox@eclipse.org" and 2) lists the communication > channels available for the individual responsible for your builds. Once this > has been done for each component on the train, I'll resolve this bug. > This has been done for OCL, UML2, UML2 Tools, and XSD. OCL: I confirm that I am now watching "cross-project.inbox@eclipse.org". I am also the person responsible for OCL builds: aigdalov@borland.com Closing, as this bug has been fixed for some time. |