From 3dbf8052ebb85d7db32961cf55d3e0071618ea5b Mon Sep 17 00:00:00 2001 From: "Michael G. Schwern" Date: Sat, 23 Jan 2010 16:26:12 -0800 Subject: [PATCH] Some updates to the patching policy --- PATCHING | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/PATCHING b/PATCHING index 94577f6..8abad62 100644 --- a/PATCHING +++ b/PATCHING @@ -21,17 +21,23 @@ of doing it. 3) DO add any new dependencies in Build.PL +3a) If you're not sure what version to depend on, pick the version + you have installed. That's safest. + 4) DON'T update MANIFEST. Its automated and will just cause conflicts. 5) DON'T update Changes. It will cause conflicts when merging. The release manager will handle it. -6) DO write tests. +6) DO write tests. Otherwise the release manager has to. + +7) DO write documentation. Otherwise the release manager has to. -7) DO write documentation. +8) Commit ONE THING AT A TIME. Preferrably use a branch for each + feature. It makes it much easier to integrate. -8) You can either send patches to schwern+perl5i@pobox.com or +9) You can either send patches to schwern+perl5i@pobox.com or (preferred) issue a github pull request. Thanks for patching!