Quote:
Originally Posted by xf117
Isn't it would be easier and more convenient to set up your development environment to compile saved script and then on success also push it in your VCS and send result via ftp?
|
I don't push every change I do to my VCS. I'm a big fan of save early, save often and its cousin compile early, compile often.
Edit: and even using this policy, PropHunt has still had 209 commits in the master branch since I started working on it a year ago.
Edit 2: 221 commits in the 3.3 branch.
Edit 3: However, if I'm switching computers, unfinished changes will be checked in, which is why new versions are developed in branches and then merged back into master. Also because people pull from my master repo and expect a version that actually works. I will also make changes to the current version in master then merge it back to the current version branch for things like configuration file changes.
__________________