20-30ish attendees
source control systems:
- subversion
* seemed to be the most common among the attendees
- tfs
- perforce
* mid range, commercial
* server system
* good at branching (integrating, versioning, etc.)
* got vs integration
* cross platform
source control clients:
- tortoise svn
- visual svn
+ dispatch to send off to different servers
-> some suggestions regarding templates and how to manage
- tfs explorer (is free and an option for non-developers)
team sizes: between 2 and 10 for the most
Build servers:
- CruisecControl.net
- TeamCity from JetBrains
- nAnt and msBuild for buildscripts
problem w/svn: designers changing templates
-> optionally lock down that section
-> tfs powertools and shell extensions (Aaron)
-> common that devs change templates!
-> no sourcecontrol -> static xhtml, convention with revisions
--
dislocated teams, content into staging
- same database?
- redgate?
- courier
* closed source
* new version in the works
* did the job more or less
- reseed really high
- redgate
- a problem upgrading existing databases
- migrate from the xml file possible (Shannon)
- one shared database
- configuration file with nodeids
remote devs and high seed db prob: individual db's
how do you incorporate website?
work item / tasks management?
--
Idea from Darren:
event handler to update environments via web services
media service is incomplete ... Thomas might have details?
package / dashboard
(Niels created a logger package - every time something was changed -> log)
--> Idea: changelog -> expose as rss?
--
manual update of doctypes etc.
--
nightly builds: cruise control, teamcity
deployment -> zipfiles (only v4)
ant scripts do the job (shannon)
--
document types as xml?
the more on the file system, the better
--
what is stored in source control
- store everything including latest v of umb
- (project startup) first person do the install and check in
* easier to upgrade as well
--
trend? some only use usercontrols and hardly any xslt (only for navigation)
--> easier to train new devs to use usercontrols
--> preview problem with xslt -> copy publish preview
Preview Idea for future release -> snapshopts of a website at a certain date
--> (Shannon) funnel all into ienumerable enabled APIs