> With Perl apps, there's no "make" and "release" -- the checked-in ["committed"] files *ARE* the app, and so part of the workflow isn't clear to me: I have the hierarchy PROJECT. PROJECT/SVN is my repository and PROJECT/PROJECT is where the actual in-production app lives [together with its various "extra" files: logs, docs, config files, etc]. I can easily right-click on SVN, do "check out a copy" into PROJECT/NEWSTUFF, play around, and then do a "commit" on the whole directory [so everything I changed and tweaked would get "checked in" -- that's the right way to do an SVN-styule workflow, yes?]
Just to clarify, because from your wording I can't tell whether you're
clear on the concept: Subversion is a client/server application. The
master copy of your repository doesn't live in PROJECT/SVN; it lives on
the server. (The server may of course be running on the same machine as
you run the client and do your work, but the server is logically
separate from your working area.)
Other than that, yes, the workflow is correct. Rightclick a folder and
then check out a working copy *from the server* to PROJECT/NEWSTUFF,
make your changes, and then commit to send your changes to the server.
When you're ready to make your changes live, copy the files from an
updated working copy to your production folder (PROJECT/PROJECT).
btw, you probably want to keep your docs and config files versioned too.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-01-20 23:45:46 CET