summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbrian d foy <brian.d.foy@gmail.com>2011-11-20 14:04:12 -0600
committerbrian d foy <brian.d.foy@gmail.com>2011-11-20 14:04:12 -0600
commit09c581faaf92ae388d006ba64648fe181e87c43a (patch)
tree4cc31e4fc1fd68248f4b0c9a1aff8579effcdef0
parent8fe0571645619844c3a4f2defc3990634138e838 (diff)
downloadperl-briandfoy/perlduallife.pod.tar.gz
A start on perlduallife.podbriandfoy/perlduallife.pod
-rw-r--r--pod/perlduallife.pod47
1 files changed, 47 insertions, 0 deletions
diff --git a/pod/perlduallife.pod b/pod/perlduallife.pod
new file mode 100644
index 0000000000..26d7997ddf
--- /dev/null
+++ b/pod/perlduallife.pod
@@ -0,0 +1,47 @@
+=encoding utf8
+
+=head1 NAME
+
+perlduallife - Maintaining a dual-lived distribution
+
+=head1 DESCRIPTION
+
+This is the owner's manual for a dual-lived module, and expands on
+L<perlpolicy> and L<perlrepository>.
+
+=head2 About dual-lived modules
+
+A dual-lived module has two tracks of developmentā€”one in the perl
+sources and one on CPAN. This typically allows you to install a newer
+version from CPAN without installing a later perl, or update a module
+without changing the perl sources. Which one you use depends on the
+interest in the distribution. An active distribution with dedicated
+maintainers probably wants to move at their own schedule and sync with
+perl at set times, so it lives primarily on CPAN. A stable
+distribution with few or minor changes and without a dedicated
+maintainer might do better inside the perl repository.
+
+=head2 Important files for the dual-lived maintainer
+
+=over
+
+=item Porting/Maintainers.pl
+
+=back
+
+=head2 The perl build process
+
+=head1 Upstream-specific instructions
+
+=head2 Upstream is perl.git
+
+
+=head2 Upstream is CPAN
+
+=head1 AUTHOR
+
+brian d foy, C<< <bdfoy@cpan.org> >>
+
+
+=cut
+