Our earlier meeting ran over. Once Cory had a chance, we went over projects and quotes and what not. One of the topics brought up was testing and pushing code. We are constantly deploying new code, pushing things up, reviewing things, and making changes. It happens all of the time.

The question and/or topic was - what are the processes and protocol for doing those changes? When should they happen? And what communications should be in place either before or after new code is pushed? That gets kinda tough and we didn't have any set in stone answers. It kinda depends on what is needed, wanted, tested, how deep, how wide, and how much each project affects the core pages and/or core logic. We chatted about some ideas and options but no firm concrete decisions were made. Lots of variables.

Steve really wants to pitch some of the VPS (virtual private server) stuff to our clients. He had some questions along those lines.