Upgrade Beta 3 to Beta 3 refresh
What will be involved in an upgrade from VSTF beta 3 to the beta 3 refresh?
We have been testing the upgrade procedure recently. Our plan is to make it as smooth as possible. Unfortunately it's going to be a bit more than uninstalling and reinstalling but not too much more. The databases have to be reattached (after SQLServer is reinstalled) and the Warehouse needs to be rebuilt.
One issue most people will face is that reports need to be reuploaded to the report server. I haven't seen the procedure for this yet but I'm told it's not bad.
The biggest issue is going to be MSF CMMI projects. It turns out that the CMMI Process template was not really ready for prime time when we shipped Beta 3 and a huge amount of work has been done to get it ready for the Beta 3 refresh. If you are using MSF Agile projects it should be seamless but we're still working through the upgrade procedure for CMMI projects.
It would be intersting to know how many people created and are really using MSF CMMI based projects.
Ahhhh..the reactive approach. Get some stats on how many are using CMMI by making it painful enough for them to cry for help. On a serious note, thanks for this info. I think I'm going to wait for the Beta 3 refresh version to come out before we start working on the planned team project using CMMI. This version should be out around Nov 7th, right?
Ouch! We're not trying to make it difficult for people and we will deliver on our promise to upgrade people's data from B3 to B3R. It's simply that we will have to put together a SQL script to transform B3 MSF CMMI work item types to B3 Refresh MSF CMMI work item types - many changes were made: field names, data types, etc. CMMI was broken enough in B3 that I'm skeptical anyone would have really created a working project using it. If not, I don't want to spend the 2 or 3 days putting together a script that no one will use. If there's even one customer who has a CMMI project they need to keep, we'll do the work.
Brian
All in jest, my friend. I do appreciate the level of commitment that MS has made to the VSTS effort. I realize that the CMMI process template is still in a state of flux. I love this product, but I also don't mind poking fun in the process.