At 2:21 PM -0700 9/21/06, Chris W. Parker wrote:
Hello,
This is off topic but I wanted to get the list member's opinions on the
subject as it will probably benefit someone else.
-snip-
Is this a sound strategy or should I just realize that I can't publish
until all current features enhancements are completed?
Thanks,
Chris.
Chris:
I've been thinking about this as well. Please forgive my naiveness if
the gang already has a better way, but the method I used to do
application development was that I started with a folder that
contained all my code, which I named v1.0.
Whenever I reached a milestone of some type I thought significant, I
duplicated the entire working folder; renamed the duplicate the next
version (i.e., v1.01); and started working with the new folder. If I
screwed up, then I could always trash the new folder, duplicate the
previous version and start again. It was a system that worked for me.
At the end of the development cycle, I would have a long thread of
development versions. Often, I found that intermediate folders
provided branches for other development -- so, keeping intermediate
development versions was a plus.
Now, it's a bit different working with folders on the web because you
have one "root" (live) folder and making changes can be problematic.
However, there's enough similarity that I often follow the same
method as I used in application development.
For example, my current site http://sperling.com is alive and running
well. However, I am doing a complete rewrite of the site. As such I
duplicated the entire site and placed it in another directory,
namely: http://sperling.com/a -- and I work on that.
When I feel that revision is ready, I will save the current "root"
directory to my desktop, delete it on my server and then pull
everything out of my "a" directory and make it the new root. For me,
that would take just a few minutes. For more complex sites, where the
change must be instant, I would look into using the .htaccess file to
change the root index.
If there are better development schemes, I would like to hear about
them as well.
Cheers,
tedd
--
-------
http://sperling.com http://ancientstones.com http://earthstones.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
