Disney Count support may be spotty from here. We apologize for the inconvenience.

To Steel, know anything about the processes

At MS for submitting code changes.  And you can just say simple or not.  Simple like subversion/cvs simple or not simple like CMMI level 6.
Permalink Send private email Bot Berlin 
September 12th, 2006 5:43pm
Do you mean for a developer on a team? Or for someone outside the team?

For the developers AFAIK it's all pretty standardized such that they spend a minimal amount of time checking stuff in and out. I also *think* they're moving from MSBuild to Team Foundation Server, but I don't know the status of that.

If you really want to know more (and have specific questions) I can ping some devs and ask.
Permalink Send private email Steel McLargeEsquimaux 
September 12th, 2006 6:06pm
>>> I can ping some

I hate that phrase.  I've only ever seen a few times and it still sounds stupid.
Permalink Send private email Wärd 
September 12th, 2006 6:39pm
I've been in IT for eleven years, spent a lot of it as a sysadmin. Before that I was an antisubmarine warfare officer.

Gonna be pretty hard to pry "ping" out of my consciousness....
Permalink Send private email Steel McLargeEsquimaux 
September 12th, 2006 7:32pm
No, no, I insist, you must change 11 years of habit for my sake.
Permalink Send private email Wärd 
September 12th, 2006 7:40pm
Just wanted to see if it as convoluted as what I am working with.  Mostly maintenance style coding.  Every change has to go through a mountain of sign-offs and promted to 4-5 different servers.  arggg..
Permalink Send private email Bot Berlin 
September 12th, 2006 7:41pm
Hrm.

Well, feature *changes* have a significant beauracracy involved, as you can imagine. Taking Word as an extreme example - any change you want in Word had to go through:
- planning
- impact analysis
- coding
- internationalization (20-something languages, I think)
- interoperability testing with other Office apps
- interoperability testing with the API's
- regression testing on existing Word documents
- regression testing on existing Word macro code
- regression testing on existing Word managed code
- interoperability and regression testing on VSTO

That's off the top of my head.
Permalink Send private email Steel McLargeEsquimaux 
September 12th, 2006 7:46pm
Interesting.

Is there a name associated with the process or a set of tools used.
Permalink Send private email Bot Berlin 
September 12th, 2006 7:49pm
Feature changes are an administrative process managed by each product group.

The mechanics of checking the code, the unit test framework, and QA used to be MSBuild, a custom in-house app. As I said - I think they're moving to TFS, but I'm not sure when.
Permalink Send private email Steel McLargeEsquimaux 
September 12th, 2006 8:10pm

This topic is archived. No further replies will be accepted.

Other topics: September, 2006 Other topics: September, 2006 Recent topics Recent topics