bmrc process notes

2
BMRC Process Notes: Release note is only appropriate to be included in a PB1411 build when the associated code is under PB1411. As your code is currently under P_TEM, it needs if not already done for the Release note to be included in a P_TEMP build. As such we will not include it in PB1411 until the code is agreed on the BAU control list for PB1411 and thus the Masters re-pointed. All, Who does Karthikeyan work for? Which Project or Team? Who is the SAP CORE sponsor for this request? Hi BMRC team, Please approve this request for providing developer access key to user NARAYAK5 in JD1 and LD1. Regards, The Planned Build Fit Testing Staging ETE is not used for IPD testing. The Regression ETE’s are ETE03 (with ETE05 as the staging ETE). ETE13 is a staging environment not a Test Environment. We use to smoke test as required and will be updated on a daily basis with PB1411 code.

Upload: rupakbhattacharjee

Post on 06-Dec-2015

213 views

Category:

Documents


0 download

DESCRIPTION

dddd

TRANSCRIPT

Page 1: BMRC Process Notes

BMRC Process Notes:

Release note is only appropriate to be included in a PB1411 build when the associated code is under PB1411. As your code is currently under P_TEM, it needs if not already done for the Release note to be included in a P_TEMP build.

As such we will not include it in PB1411 until the code is agreed on the BAU control list for PB1411 and thus the Masters re-pointed.

All,

Who does Karthikeyan work for?

Which Project or Team?

Who is the SAP CORE sponsor for this request?

Hi BMRC team,

Please approve this request for providing developer access key to user NARAYAK5 in JD1 and LD1.

Regards,

The Planned Build Fit Testing Staging ETE is not used for IPD testing.

The Regression ETE’s are ETE03 (with ETE05 as the staging ETE).

ETE13 is a staging environment not a Test Environment.

We use to smoke test as required and will be updated on a daily basis with PB1411 code.

If this is an IPD then the Test Environment that is allocated is ETE03 and that gets deployed via P_TEMP builds.