SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm putting together a release process for our SharePoint 2007 environment. We have admins and power users who have to make out of the box changes to sites via the browser. Only one admin who can make some custom authored Workflows in SharePoint Designer 2007. Both admins and also a few power users who will soon author and publish InfoPath 2007 to both TEST and LIVE (they're currently in training). The Development team can also create custom WSPs. So from above we three types of change

  1. Out of the Box
  2. SharePoint Designer and InfoPath
  3. WSPs

We get a lot of request for changes mostly for new sites with libraries and list (some with custom workflows) and also using content types, content roll ups using the Content Query Web Part and the summary links web parts.

Basically we don't want overkill on perhaps the out of the box changes. But I'd be interested knowing what tests plans and rollback steps others are using for their release process for each of the above senarios

Thanks in advance!

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.