Support Certification Setup

[ibuchanan]

As a tester or support engineer, I want to quickly create an environment that meets user requirements so that I can check the integration is working correctly (see specs from issue #27).

Acceptance Criteria:

• Environment definition is in the repo and documented in the README.
• A fresh Windows VM (including Service Packs).
• A VersionOne instance with a known URL.
• Required packages (as listed in user docs).

Possible solutions:

• Spin up VM on AWS.
• Use Puppet or Chef to declare dependencies (compare/contrast, then pick one)
• Use Chocolatey to supply dependencies

How Mark will evaluate the release:

• Install it.
• Connect to VersionOne.
• Do what docs say.

[ibuchanan]

Once we can create "disposable" VMs with VS, there won't be any reason to keep any VMs on puregold for testing of VS. So tear it down if we don't need it. (Like clean up of dead code.)

[ibuchanan]

Mark will need quality band definition. We will need to supply him with the App Catalog Staging link so he can come in through the "front door". Then he will apply it to the environment he creates.

[jkoberg]

What are the user requirements? Some versions of windows have pre-spun AMI images ready to go, but some have to be created.

Do we need to tool up images for Windows Vista, Windows 7, Server 2003, Server 2008, Server 2012, etc?

[ibuchanan]

Just as we narrowed the scope for this first release to just VS 2012 and just Pro and Prem Editions, let's narrow the options here too. The data we have points to Windows 7 as the largest target. I'll note that in the user docs.

[JogoShugh]

Process for doing the certification is outlined at https://github.com/versionone/VersionOne.Client.VisualStudio/wiki/Support-Certification-of-VS-Client-Outline

[ibuchanan]

Held our first certification session yesterday. All parties got value out of it. We'll take this ceremony as part of our regular release process.