summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAbigail <abigail@abigail.be>2012-03-19 11:14:15 +0100
committerAbigail <abigail@abigail.be>2012-03-19 11:14:15 +0100
commit8cfc9af613d5c73745f210535cf8921067507306 (patch)
treeb71f74e0973531e9258e3d29f295b8a2ca67b3e7
parentc9ebf02397fb525998acacd7b4ac9a55323b54ab (diff)
downloadperl-8cfc9af613d5c73745f210535cf8921067507306.tar.gz
More work on perldelta
-rw-r--r--pod/perldelta.pod99
1 files changed, 15 insertions, 84 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 0041461e31..6ada4878a5 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -26,26 +26,15 @@ features (which is likely to be a pretty special-purpose request, since
it presumably won't match any named set of semantics) you can now
write C<< no feature ':all' >>.
-
-[ List each enhancement as a =head2 entry ]
-
=head1 Security
-XXX Any security-related notices go here. In particular, any security
-vulnerabilities closed should be noted here rather than in the
-L</Selected Bug Fixes> section.
-
-[ List each security issue as a =head2 entry ]
+There have been no security related fixed between 5.15.8 and 5.15.9.
=head1 Incompatible Changes
-XXX For a release on a stable branch, this section aspires to be:
+=head2 C<< no feature; >>
- There are no changes intentionally incompatible with 5.XXX.XXX
- If any exist, they are bugs, and we request that you submit a
- report. See L</Reporting Bugs> below.
-
-[ List each incompatible change as a =head2 entry ]
+C<no feature;> now means reset to default.
=head1 Deprecations
@@ -121,32 +110,8 @@ XXX
=head1 Documentation
-XXX Changes to files in F<pod/> go here. Consider grouping entries by
-file and be sure to link to the appropriate page, e.g. L<perlfunc>.
-
-=head2 New Documentation
-
-XXX Changes which create B<new> files in F<pod/> go here.
-
-=head3 L<XXX>
-
-XXX Description of the purpose of the new file here
-
-=head2 Changes to Existing Documentation
-
-XXX Changes which significantly change existing files in F<pod/> go here.
-However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
-section.
-
-=head3 L<XXX>
-
-=over 4
-
-=item *
-
-XXX Description of the change here
-
-=back
+There has been no significant change in the documentation between
+5.15.8 and 5.15.9.
=head1 Diagnostics
@@ -213,37 +178,8 @@ C<STDIN> had been closed.
=head1 Platform Support
-XXX Any changes to platform support should be listed in the sections below.
-
-[ Within the sections, list each platform as a =item entry with specific
-changes as paragraphs below it. ]
-
-=head2 New Platforms
-
-XXX List any platforms that this version of perl compiles on, that previous
-versions did not. These will either be enabled by new files in the F<hints/>
-directories, or new subdirectories and F<README> files at the top level of the
-source tree.
-
-=over 4
-
-=item XXX-some-platform
-
-XXX
-
-=back
-
-=head2 Discontinued Platforms
-
-XXX List any platforms that this version of perl no longer compiles on.
-
-=over 4
-
-=item XXX-some-platform
-
-XXX
-
-=back
+There have been no changes to Perl's support of various platforms between
+5.15.8 and 5.15.9.
=head2 Platform-Specific Notes
@@ -332,27 +268,22 @@ C<< Term::ReadLine >> now uses AnyEvent instead of Tk for an event loop.
=head1 Known Problems
-XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
-tests that had to be C<TODO>ed for the release would be noted here, unless
-they were specific to a particular platform (see below).
-
This is a list of some significant unfixed bugs, which are regressions
-from either 5.XXX.XXX or 5.XXX.XXX.
-
-[ List each fix as a =item entry ]
+from either 5.14.0 or 5.15.8.
=over 4
-=item *
+=item C<eval { 'fork()' }> is broken on Windows [perl #109718]
-XXX
+This is a known test failure to be fixed before 5.16.0.
-=back
+=item C<< Pod-Html >> test failures on Windows.
-=head1 Obituary
+A number of tests for C<< Pod::Html >> fail under Windows, due to an
+incorrect assumption by the test scripts about capitalization of the
+network drive.
-XXX If any significant core contributor has died, we've added a short obituary
-here.
+=back
=head1 Acknowledgements