DevelopmentStagingProcess

Revision as of 23:43, 2 October 2007 by Jason Parmer (talk | contribs)



DevelopmentTeam Edit-chalk-10bo12.png

What (summary)

  • Immediate action when necessary
  • A platform to incrementally release and user test things before they go live

Why this is important

  • Not surprising users in "a bad way"
  • Rarely make "mistakes"
  • Getting better at communicating with our users so they know when things are about to be installed

Tasks

  1. We should toss up a solution that makes sense to us ... DevTools
  2. Then convene a meeting of all stakeholders to discuss our prototype staging process and whether there are tweaks we should introduce

Stuff

  • easy script to create a branch
    • make sure it doesn't conflict with an existing branch name
    • branch aboutus and compost
  • easy script to make a branch active on your (the developers) box
  • branch serving on till
    • port allocation for compost mongrels
    • apache config
  • easy revert for when things get hosed (tags?)
  • Ability to see what has been running on the live site (date based tags would be fine, possibly a log of hashes or whatever)
  • easy script to merge + close branches


Retrieved from "http://aboutus.com/index.php?title=DevelopmentStagingProcess&oldid=11363039"