1Patching instructions for Search-Dict
2
31. Check for any changes to .pm files since dev or stable Perl release.  E.g.
4to check for changes since v5.15.8:
5
6    $ cd dist/g
7    $ git log v5.15.8..blead -- .
8
92. If you are making the first change since the last Perl release, you need to
10bump the $VERSION in all .pm files and update the Changes file with the new
11version.  In the Changes file, put the expected *NEXT* release of Perl (dev or
12stable) as the release date and version.  E.g. after v5.15.8, I would add this line
13to Changes to indicate what will be next release:
14
15    0.280206 - 2012-03-20 (Perl v5.15.9)
16
173. Add an entry to Changes for your work
18
194. Update Makefile.PL, MANIFEST.SKIP or other support files as necessary. E.g.
20update Makefile.PL with any changes to prerequisites.
21
225. Commit all changes (preferably to a branch)
23
246. Run Configure/make/make test and check for errors.  If there are any, fix them.
25
267. If all is well, push your commits to blead or send a patch to p5p if you do
27not have commit access to the Perl 5 repository
28