Here is my first cut.
(a) Check the state of the immediate next release/releases with the Project Mgr.
i.e. what is the status of
SPRs and features targetted.
(b) Work on release test plan and release test platform/tools. Identify new
requirements and new tests that
have to be done.
(c) Check the status of major SPRs or features in conjunction with technical
lead. I.e. what level of maturity
they are at, whether they can be preponed to an earlier release or have to be
postponed to a latter release,
etc.
(d) Work with CM on the build and archiving process. This would include
verifying the combination of s/w
packages, verifying the versions of the source that gets built, etc.
(e) Work with SQA on the Verification Testing schedules and resources
(f) Work with Lab-In-Charge for scheduling resources and lab time for release
testing.
(g) Work with Publications for release specific documentation i.e. release
notes.
That wouldn't be a bad start.
Regards,
Abheek
"xu zhe" <daxu@hotmail.com> on 01/13/2000 08:34:50 AM
To: cciug@Rational.Com
cc: (bcc: Abheek Saha/HSS)
Subject: [cciug] what is the responsibility of release engineer?
Hello,
Can anyone tell me what the responsibility a release engineer is? What does
he do daily?Is it Interesting?
Best Regards,
Frank Xu
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:26 EDT