diff options
| author | Neil Bowers <neil@bowers.com> | 2013-07-21 20:59:20 +0100 |
|---|---|---|
| committer | Tony Cook <tony@develop-help.com> | 2013-07-24 11:10:50 +1000 |
| commit | 4a8dd740b55a404b1284797635911b22a8dd7013 (patch) | |
| tree | 0d9c43b292fc911eda6d20dc7e8163c8fe2dcc6d /pod/perlmodstyle.pod | |
| parent | d2ae0270dadf4ccfaea97b4a0c962867d19e1e72 (diff) | |
| download | perl-4a8dd740b55a404b1284797635911b22a8dd7013.tar.gz | |
For changelogs suggest name it Changes and follow CPAN::Changes::Spec
Diffstat (limited to 'pod/perlmodstyle.pod')
| -rw-r--r-- | pod/perlmodstyle.pod | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/pod/perlmodstyle.pod b/pod/perlmodstyle.pod index 558642c2fb..5622d3244d 100644 --- a/pod/perlmodstyle.pod +++ b/pod/perlmodstyle.pod @@ -598,6 +598,11 @@ Release notes or changelogs should be produced for each release of your software describing user-visible changes to your module, in terms relevant to the user. +Unless you have good reasons for using some other format +(for example, a format used within your company), +the convention is to name your changelog file C<Changes>, +and to follow the simple format described in L<CPAN::Changes::Spec>. + =head1 RELEASE CONSIDERATIONS =head2 Version numbering |