@@ -1,5 +1,8 @@
 Revision history for DBIx-Class-DeploymentHandler
 
+0.002213  2014-12-03 08:44:10-06:00 America/Chicago
+ - Fix some POD formatting
+
 0.002212  2014-10-11 15:04:22-05:00 America/Chicago
  - Add some nice documentation on overall structure
 

@@ -67,6 +67,6 @@
          "web" : "https://github.com/frioux/DBIx-Class-DeploymentHandler"
       }
    },
-   "version" : "0.002212"
+   "version" : "0.002213"
 }
 

@@ -39,4 +39,4 @@ resources:
   bugtracker: https://github.com/frioux/DBIx-Class-DeploymentHandler/issues
   homepage: https://github.com/frioux/DBIx-Class-DeploymentHandler
   repository: https://github.com/frioux/DBIx-Class-DeploymentHandler.git
-version: '0.002212'
+version: '0.002213'

@@ -45,7 +45,7 @@ my %WriteMakefileArgs = (
     "Test::Requires" => "0.06",
     "aliased" => 0
   },
-  "VERSION" => "0.002212",
+  "VERSION" => "0.002213",
   "test" => {
     "TESTS" => "t/*.t t/bugs/*.t t/deploy_methods/*.t t/version_handlers/*.t t/version_storages/*.t"
   }

@@ -2,7 +2,7 @@ name             = DBIx-Class-DeploymentHandler
 author           = Arthur Axel "fREW" Schmidt <frioux+cpan@gmail.com>
 license          = Perl_5
 copyright_holder = Arthur Axel "fREW" Schmidt
-version          = 0.002212
+version          = 0.002213
 
 [NextRelease]
 [@Git]

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::Cookbook::CustomResultSource;
-$DBIx::Class::DeploymentHandler::Cookbook::CustomResultSource::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::Cookbook::CustomResultSource::VERSION = '0.002213';
 # ABSTRACT: Customize how your DBICDH versions are stored
 
 __END__

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::Dad;
-$DBIx::Class::DeploymentHandler::Dad::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::Dad::VERSION = '0.002213';
 # ABSTRACT: Parent class for DeploymentHandlers
 
 use Moose;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::Deprecated;
-$DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::Deprecated::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::Deprecated::VERSION = '0.002213';
 use Moose;
 
 # ABSTRACT: (DEPRECATED) Use this if you are stuck in the past

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::ScriptHelpers;
-$DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::ScriptHelpers::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::ScriptHelpers::VERSION = '0.002213';
 # ABSTRACT: CodeRef Transforms for common use-cases in DBICDH Migrations
 
 use strict;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator;
-$DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::DeployMethod::SQL::Translator::VERSION = '0.002213';
 use Moose;
 
 # ABSTRACT: Manage your SQL and Perl migrations in nicely laid out directories
@@ -847,65 +847,80 @@ The following subdirectories are recognized by this DeployMethod:
 
 =over 2
 
-=item C<_source> This directory can contain the following directories:
+=item C<_source>
+
+This directory can contain the following directories:
 
 =over 2
 
-=item C<deploy> This directory merely contains directories named after schema
+=item C<deploy>
+
+This directory merely contains directories named after schema
 versions, which in turn contain C<yaml> files that are serialized versions
 of the schema at that version.  These files are not for editing by hand.
 
 =back
 
-=item C<_preprocess_schema> This directory can contain the following
-directories:
+=item C<_preprocess_schema>
+
+This directory can contain the following directories:
 
 =over 2
 
-=item C<downgrade> This directory merely contains directories named after
-migrations, which are of the form C<$from_version-$to_version>.  Inside of
-these directories you may put Perl scripts which are to return a subref
-that takes the arguments C<< $from_schema, $to_schema >>, which are
-L<SQL::Translator::Schema> objects.
+=item C<downgrade>
+
+This directory merely contains directories named after migrations, which are of
+the form C<$from_version-$to_version>.  Inside of these directories you may put
+Perl scripts which are to return a subref that takes the arguments C<<
+$from_schema, $to_schema >>, which are L<SQL::Translator::Schema> objects.
 
-=item C<upgrade> This directory merely contains directories named after
-migrations, which are of the form C<$from_version-$to_version>.  Inside of
-these directories you may put Perl scripts which are to return a subref
-that takes the arguments C<< $from_schema, $to_schema >>, which are
-L<SQL::Translator::Schema> objects.
+=item C<upgrade>
+
+This directory merely contains directories named after migrations, which are of
+the form C<$from_version-$to_version>.  Inside of these directories you may put
+Perl scripts which are to return a subref that takes the arguments C<<
+$from_schema, $to_schema >>, which are L<SQL::Translator::Schema> objects.
 
 =back
 
-=item C<$storage_type> This is a set of scripts that gets run depending on what
-your storage type is.  If you are not sure what your storage type is, take a
-look at the producers listed for L<SQL::Translator>.  Also note, C<_common>
-is a special case.  C<_common> will get merged into whatever other files you
-already have.  This directory can contain the following directories itself:
+=item C<$storage_type>
+
+This is a set of scripts that gets run depending on what your storage type is.
+If you are not sure what your storage type is, take a look at the producers
+listed for L<SQL::Translator>.  Also note, C<_common> is a special case.
+C<_common> will get merged into whatever other files you already have.  This
+directory can contain the following directories itself:
 
 =over 2
 
-=item C<initialize> Gets run before the C<deploy> is C<deploy>ed.  Has the
-same structure as the C<deploy> subdirectory as well; that is, it has a
-directory for each schema version.  Unlike C<deploy>, C<upgrade>, and C<downgrade>
-though, it can only run C<.pl> files, and the coderef in the perl files get
-no arguments passed to them.
-
-=item C<deploy> Gets run when the schema is C<deploy>ed.  Structure is a
-directory per schema version, and then files are merged with C<_common> and run
-in filename order.  C<.sql> files are merely run, as expected.  C<.pl> files are
-run according to L</PERL SCRIPTS>.
-
-=item C<upgrade> Gets run when the schema is C<upgrade>d.  Structure is a directory
-per upgrade step, (for example, C<1-2> for upgrading from version 1 to version
-2,) and then files are merged with C<_common> and run in filename order.
-C<.sql> files are merely run, as expected.  C<.pl> files are run according
-to L</PERL SCRIPTS>.
-
-=item C<downgrade> Gets run when the schema is C<downgrade>d.  Structure is a directory
-per downgrade step, (for example, C<2-1> for downgrading from version 2 to version
+=item C<initialize>
+
+Gets run before the C<deploy> is C<deploy>ed.  Has the same structure as the
+C<deploy> subdirectory as well; that is, it has a directory for each schema
+version.  Unlike C<deploy>, C<upgrade>, and C<downgrade> though, it can only run
+C<.pl> files, and the coderef in the perl files get no arguments passed to them.
+
+=item C<deploy>
+
+Gets run when the schema is C<deploy>ed.  Structure is a directory per schema
+version, and then files are merged with C<_common> and run in filename order.
+C<.sql> files are merely run, as expected.  C<.pl> files are run according to
+L</PERL SCRIPTS>.
+
+=item C<upgrade>
+
+Gets run when the schema is C<upgrade>d.  Structure is a directory per upgrade
+step, (for example, C<1-2> for upgrading from version 1 to version 2,) and then
+files are merged with C<_common> and run in filename order.  C<.sql> files are
+merely run, as expected.  C<.pl> files are run according to L</PERL SCRIPTS>.
+
+=item C<downgrade>
+
+Gets run when the schema is C<downgrade>d.  Structure is a directory per
+downgrade step, (for example, C<2-1> for downgrading from version 2 to version
 1,) and then files are merged with C<_common> and run in filename order.
-C<.sql> files are merely run, as expected.  C<.pl> files are run according
-to L</PERL SCRIPTS>.
+C<.sql> files are merely run, as expected.  C<.pl> files are run according to
+L</PERL SCRIPTS>.
 
 =back
 

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::Deprecated;
-$DBIx::Class::DeploymentHandler::Deprecated::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::Deprecated::VERSION = '0.002213';
 # ABSTRACT: (DEPRECATED) Use this if you are stuck in the past
 
 use Moose;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::HandlesDeploy;
-$DBIx::Class::DeploymentHandler::HandlesDeploy::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::HandlesDeploy::VERSION = '0.002213';
 use Moose::Role;
 
 # ABSTRACT: Interface for deploy methods

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::HandlesVersionStorage;
-$DBIx::Class::DeploymentHandler::HandlesVersionStorage::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::HandlesVersionStorage::VERSION = '0.002213';
 use Moose::Role;
 
 # ABSTRACT: Interface for version storage methods

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::HandlesVersioning;
-$DBIx::Class::DeploymentHandler::HandlesVersioning::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::HandlesVersioning::VERSION = '0.002213';
 use Moose::Role;
 
 # ABSTRACT: Interface for version methods

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::LogImporter;
-$DBIx::Class::DeploymentHandler::LogImporter::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::LogImporter::VERSION = '0.002213';
 use warnings;
 use strict;
 

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::LogRouter;
-$DBIx::Class::DeploymentHandler::LogRouter::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::LogRouter::VERSION = '0.002213';
 use Moo;
 use DBIx::Class::DeploymentHandler::Logger;
 

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::Logger;
-$DBIx::Class::DeploymentHandler::Logger::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::Logger::VERSION = '0.002213';
 use warnings;
 use strict;
 

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::Manual::CatalystIntro
-$DBIx::Class::DeploymentHandler::Manual::CatalystIntro::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::Manual::CatalystIntro::VERSION = '0.002213';
 # ABSTRACT: Introduction to using DBIx::Class::DeploymentHandler with a new Catalyst Project
 
 __END__

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::Manual::Intro
-$DBIx::Class::DeploymentHandler::Manual::Intro::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::Manual::Intro::VERSION = '0.002213';
 # ABSTRACT: Introduction to DBIx::Class::DeploymentHandler
 
 __END__

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::Types;
-$DBIx::Class::DeploymentHandler::Types::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::Types::VERSION = '0.002213';
 use strict;
 use warnings;
 

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionHandler::DatabaseToSchemaVersions;
-$DBIx::Class::DeploymentHandler::VersionHandler::DatabaseToSchemaVersions::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionHandler::DatabaseToSchemaVersions::VERSION = '0.002213';
 use Moose;
 
 # ABSTRACT: Go straight from Database to Schema version

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionHandler::ExplicitVersions;
-$DBIx::Class::DeploymentHandler::VersionHandler::ExplicitVersions::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionHandler::ExplicitVersions::VERSION = '0.002213';
 use Moose;
 
 # ABSTRACT: Define your own list of versions to use for migrations

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionHandler::Monotonic;
-$DBIx::Class::DeploymentHandler::VersionHandler::Monotonic::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionHandler::Monotonic::VERSION = '0.002213';
 use Moose;
 
 # ABSTRACT: Obvious version progressions

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::Component;
-$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::Component::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::Component::VERSION = '0.002213';
 # ABSTRACT: (DEPRECATED) Attach this component to your schema to ensure you stay up to date
 
 use strict;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VersionResult;
-$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VersionResult::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VersionResult::VERSION = '0.002213';
 # ABSTRACT: (DEPRECATED) The old way to store versions in the database
 
 use strict;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VersionResultSet;
-$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VersionResultSet::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VersionResultSet::VERSION = '0.002213';
 # ABSTRACT: (DEPRECATED) Predefined searches to find what you want from the version storage
 
 use strict;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Deprecated;
-$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Deprecated::VERSION = '0.002213';
 use Moose;
 use DBIx::Class::DeploymentHandler::LogImporter ':log';
 

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Standard::Component;
-$DBIx::Class::DeploymentHandler::VersionStorage::Standard::Component::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Standard::Component::VERSION = '0.002213';
 # ABSTRACT: Attach this component to your schema to ensure you stay up to date
 
 use strict;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Standard::VersionResult;
-$DBIx::Class::DeploymentHandler::VersionStorage::Standard::VersionResult::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Standard::VersionResult::VERSION = '0.002213';
 # ABSTRACT: The typical way to store versions in the database
 
 use strict;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Standard::VersionResultSet;
-$DBIx::Class::DeploymentHandler::VersionStorage::Standard::VersionResultSet::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Standard::VersionResultSet::VERSION = '0.002213';
 # ABSTRACT: Predefined searches to find what you want from the version storage
 
 use strict;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::VersionStorage::Standard;
-$DBIx::Class::DeploymentHandler::VersionStorage::Standard::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VersionStorage::Standard::VERSION = '0.002213';
 use Moose;
 use DBIx::Class::DeploymentHandler::LogImporter ':log';
 

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::WithApplicatorDumple;
-$DBIx::Class::DeploymentHandler::WithApplicatorDumple::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::WithApplicatorDumple::VERSION = '0.002213';
 use MooseX::Role::Parameterized;
 use Module::Runtime 'use_module';
 use namespace::autoclean;

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler::WithReasonableDefaults;
-$DBIx::Class::DeploymentHandler::WithReasonableDefaults::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::WithReasonableDefaults::VERSION = '0.002213';
 use Moose::Role;
 
 # ABSTRACT: Make default arguments to a few methods sensible

@@ -1,5 +1,5 @@
 package DBIx::Class::DeploymentHandler;
-$DBIx::Class::DeploymentHandler::VERSION = '0.002212';
+$DBIx::Class::DeploymentHandler::VERSION = '0.002213';
 # ABSTRACT: Extensible DBIx::Class deployment
 
 use Moose;