All evaluation and preparation tasks (5-11) done. Markku's final report reviewed, copy translated to HTML and placed on king database.
Most immediate tasks (12-41) completed, with the following exceptions:
LAN monitoring initiated by Jan-Erik Sarparanta.
Release engineering in Armas3 started by Juha Särestöniemi concurrently with this project. Build fails due to component configuration. Juha's report to Claude (Fri, 12 Mar 1999):
1) DONE THIS WEEK: - Installation and training of TAS [Cbo: TAS = TotalNet Advanced Server, by Syntax]. - Some building for Armas3... no success some of the components need to be updated... - Checked the upgrade the infra status with you.
Release engineering in 3G started by Yingfan Liu. The actual job has not really started.
Installation and test of ClearCase NT Client 3.2 on Juha S's machine brought up a surprising problem in TAS actual compatibility with HP-UX11 and ClearCase.
The fact comes from Syntax product engineering responsible person for handling the Rational-Syntax relationship who says:
From: Juha Särestöniemi [mailto:[email protected]] Sent: Thursday, March 18, 1999 10:57 AM To: petersen Cc: [email protected]; [email protected]; [email protected]; Marc Girod; Claude Bouillin Subject: Re: CaseID: v0201841: Setup of TAS (test site TAS on HP) [...] On Thu, 18 Mar 1999, Mads Petersen wrote: > Dear Juha. [...] > The paper states that we only support TAS on Solaris. It is my > understanding, that you are aware of, that the setup you are running > (with TAS on HP) is in a testcase, and that there might be issues that > is not known yet. [...]Juha says in short:
Date: Fri, 19 Mar 1999 09:52:58 +0200 (EET) From: Juha SärestöniemiTo: Carlos Bolado Subject: RE: CaseID: v0201841: Setup of TAS (test site TAS on HP) In-Reply-To: <006f01be712e$226dad40$a6eb5c8b@carlospc> X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by stybba.ntc.nokia.com id JAA14554 Hi ! I heard from Markku Tiainen that TAS will support HP-UX and NT ClearCase some time in April - June. So what we have decided to do, is to wait for that. Unless there's another solution you wish to success. We are freezing our purchase of TAS licenses. Till the time we have a possibility to test a working version with NT ClearCase. I hope we are kept up to date on the information concerning these products since we are still interested in buying TAS. Juha Särestöniemi
Status | Work Left % | |
---|---|---|
Draft SCM instructions on-line and key persons of main projects trained | SCM IB main page published and taken in use by 3G, Armas3, and GPRS. Feedback going on from each project. | 70% |
SCM operation model approved (responsibilities, roles) | Page done, linked to SCM IB main page. No feedback yet. | 90% |
New development machines installed and in use in Armas3, GPRS BB Management for T11.5 and Voitto projects | Feanor, sirion & mahtan ready for Voitto and Armas3. Feedback going on from Voitto abd Armas3. Feedback going on from each project. | 60% |
Problems: -
Feedbacks from projects don't seem to actually progress. It seems in particular that the Release Engineer role has not been clearly enough defined.
SCM Operation Model approval unclear.
New development machines actual implementation going fine. There seems to be a small problem in communicating the actual work progress toward projects.
Status | Work Left % | |
---|---|---|
Draft SCM instructions on-line and key persons of main projects trained | Feedback going on from AN3. Voitto training planned 23.4.1999 | 10% |
SCM operation model approved (responsibilities, roles) | Presentation done to GPRS & AN3. Positive feedback received from AN3. Approval pending. | 5% |
New development machines installed and in use in Armas3, GPRS BB Management for T11.5 and Voitto projects | All VOBS moved to server feanor. Old server jeeves successfully removed from SW development environment 16.4.1999. No interruption in global development process. | 0% |
Problems: -
Feedbacks from GPRS and 3G projects cannot progress before their own IT entry. AN3 feedback very useful.
SCM Operation Model approval still to be done, but eased by the fact Juha Särestöniemi kept a presentation to Merja Arppe (R&D), Veikko Kehä (GPRS) and Juha Asunmaa (AN3). The on-line model seems to be accepted by these persons.
New development machines installation very successfully concluded. Thanks to Marko Pölönen, Marc Girod, Jukka Papunen, Ville Warsta, and Timo Nuutinen.
Claude and Kalle agreed to set up a simple approval method well adapted to the project Bonus second target:
The SCM Operation Model feedbacks, send by 27 April 1999 to Kalle by all persons involved in the approval process have been quite positive. Partially because of the training and partially because of the existence of the new role in building, the Release Engineer.
The new role has been accepted gladly since it focuses the responsibility to only one person at a time. So SCM function can focus the training and get better results.
At present time, only one person, Yingfan Liu, has got the complete training for release engineer and she has proven that the task of the release engineer is easy to learn and doesn't demand too much time.
Yingfan has been able to make AN3 release builds so we consider her fully trained by Juha Särestöniemi.
A slight concern that Juha Asunmaa had, was about further development of the SCM implementation in the future: good knowledge of ClearCase and Unix systems are certainly to be required. That can be achieved only by continuous training and experience acquisition within projects. The training is and will be provided by the SCM function and experience increases every day.
Status | Work Left % | |
---|---|---|
Draft SCM instructions on-line and key persons of main projects trained | Voitto and most AN3 and GPRS project people trained as planned. | 0% |
SCM operation model approved (responsibilities, roles) | Formal approval pending. | 0% |
New development machines installed and in use in Armas3, GPRS BB Management for T11.5 and Voitto projects | 0% |
Problems: -
This project has reached a stable state. This state is not completed. That means the project can be resumed at any time in order to achieve further -though yet now undefined- goals.
In any case, maintenance and induction tasks, continuous by nature and defined as background tasks in the project task list go on according to their original definitions.