Stage each project to a separate top-level directory named after the release tag (you're of course tagging your revisions; or at best name it after the revision it corresponds to). Use svn export if you're really paranoid to completely break any ties back into a repository from live code. Symlink the "real" path to that project back to the current version. That way you can easily switch between versions by repointing symlinks, plus with judicious environment twiddling (see Envy from CPAN; it's a bit long in the tooth but works fairly well once you get it configured to your liking) you can point to a specific release if need be while not affecting the "default" version.
The cake is a lie.
The cake is a lie.
The cake is a lie.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|