Bryan Tong Minh wrote:
The simplest way would be to have the output of svn status -v on a public place along with svn diff (for live hacks). This could probably be easily incorporated in the script that is used for syncing.
Live hacks are strongly discouraged; the source should always be totally clean on a 'svn diff' though in practice there's usually something little here and there.
Individual high-priority fixes or new extensions being fixed up for deployment are often svn up'd or svn merge'd in temporarily before the next full update, though it's not an ideal practice.
But since there aren't *supposed* to be any differences between development trunk and deployment, maintaining a deployment branch seems like it could be a bit awkward... but might be better than pretending. :)
-- brion