Add some draft notes about how we do P::C releases

diff --git a/MANIFEST.SKIP b/MANIFEST.SKIP
index 8cc9a58..4550a58 100644 (file)
--- a/MANIFEST.SKIP
+++ b/MANIFEST.SKIP
@@ -1,5 +1,6 @@
 ^Perl-Critic-
 ^README\.developer$
+^README\.release$
 \.PPI$
 ^lib/Perl/Critic/PolicySummary.pod$
 _without_optional_dependencies.t$

diff --git a/README.developer b/README.developer
index 9bae95d..478224e 100644 (file)
--- a/README.developer
+++ b/README.developer
@@ -16,3 +16,4 @@ Steps for adding a new Policy:
  * tools/svnkeywords t/[category]/[name].run lib/Perl/Critic/Policy/[category]/[name].pm
 
  * Remove from TODO
+ * After release, set co-maint in PAUSE

diff --git a/README.release b/README.release
new file mode 100644 (file)
index 0000000..90c4b2b
--- /dev/null
+++ b/README.release
@@ -0,0 +1,15 @@
+These are recommended steps to performing a Perl::Critic release to CPAN.
+
+** TODO: this is just a rough draft with some ideas.  This needs to be
+   filled out by an expert.
+
+ * Pre-release
+   - testing
+   - author testing
+   - Build distmeta
+   - Build manifest
+ * Release tools
+   - ??? (chris uses cpan-upload)
+ * Post-release
+   - announce?
+   - set co-maint in PAUSE for any new modules