﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
48	Make a sane development workflow	price	broder	"Running at Packaging Capability Level AAA --- i.e., putting every change we make into a Debian package --- turns out to mean more overhead work than we're collectively willing to do, so that many things actually wind up in random SVN checkouts in people's home directories.  We should find a lower-overhead way of working while in development, one that keeps things sanely source-controlled and reproducible and that we're actually willing to keep to.  When the service is mature, like scripts.mit.edu as of 2006 rather than as of 2004, then we might move back to a higher-development-overhead, super-packaged style of operation.

Probably this means having canonical checkouts in places like /srv of purpose-made directories in SVN, so that fully integrating a change means a commit, a svn update in the canonical checkout, and perhaps a launch from there.
"	defect	closed	minor		other		fixed		
