[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Fwd: TortoiseSVN - Migration to Microsoft Vista & Office 2007]

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-06-12 17:36:42 CEST

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

attached mail follows:

Dear Tigris.Org,

Purpose of this note
This note is to inform you that the Shell Group will be migrating from Windows 2000 to Microsoft's new operating system known as Windows Vista with effect from Q1 2008, and to seek your assistance and support in minimising disruption to users and applications during and after the migration.

Between Feb - Nov 2007, we will be conducting integrated testing of our existing applications against the Windows Vista Release-to-Manufacture (RTM) edition of this operating system.

The Windows Vista 32-bit platform will initially be offered as the standard within Shell, but provision will also be made to accommodate existing and new 64-bit applications.
In addition to migrating to Windows Vista, Microsoft Office 2007 will also replace Office 2000 as the standard Office suite in the Shell Group. This means that any application in the Group that requires any Microsoft Office application/tool to function fully must be compatible with the Application Programming Interface (API) or components of Office 2007.

What we need from you
One of the key pre-requisites in migrating to the new platform as described above is to ensure that all applications and middleware currently used in the Shell Group continue to be available and fully supported in the Microsoft Vista environment.

The following product(s) from your organisation are currently in use in Shell and fall into the category of applications that need to undergo the application compatibility testing
Product(s) Version
Subversion 1.4.3
TortoiseSVN 1.4.3

1. For the product(s) listed above, kindly provide the following information by 20th June 2007:

i) version that will be Vista-certified - this means that the application should conform to the Microsoft Windows Vista Compliance Logo Guidelines, details of which are available in the Microsoft Logo Compliance website via <https://partner.microsoft.com/global/40025156>

ii) if the version referred to in (i) above is compatible with Office 2007 (if required)

iii) if the version referred to in (i) above is offered in 32-bit or 64-bit code (or both)

iv) if and when a Vista release of the version referred to in (i) above can be made available to Shell for the purposes of internal application compatibility testing (if this version is yet to be released to the market)

v) any specific middleware requirements (including version/release numbers) & dependencies

2. Appoint one contact person from your organisation to be the main liaison for ALL matters pertaining to Vista compatibility and timeline issues. Once he/she has been appointed, kindly provide his/her contact details to the undersigned.

Additional Information
1. If you are unfamiliar with Microsoft Vista or need to have more information about this platform, please refer to the Microsoft Vista website: <http://www.microsoft.com/windowsvista/default.aspx>
2. Further information on Office 2007 can be found at: <http://www.microsoft.com/office/preview/default.mspx>
3. Below is a Shell EP Basic Technical Information for your guidance in Shell GID environment.
 <<GI-NG Basic environmental information for Third Party Vendors.ZIP>>

Please contact me if you have any questions or concerns and we look forward to working closely with you.
Thank you for your attention and action.

Kind regards,
Neeza Nekmat
Norhanizah Nekmat
EP GI-NG Vendors Communication
Shell International Exploration and Production

Email: Norhanizah.N.Nekmat@shell.com
Office: +31 70 447 7294
Fax: +31 70 447 2982
Address: PO Box 60, 2280 AB Rijswijk, The Netherlands

Received on Tue Jun 12 17:42:07 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.