From 8e967a1c9f35e7fd5c203418cf4d7abc39df847b Mon Sep 17 00:00:00 2001 From: David Golden Date: Tue, 29 Jun 2010 22:40:03 -0400 Subject: update release manager instructions for a new perldelta --- Porting/release_managers_guide.pod | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) (limited to 'Porting/release_managers_guide.pod') diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 4e23e7e14d..79e49b4daf 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -904,9 +904,24 @@ see F. You should be able to do this by just copying in a skeleton template and then doing a quick fix up of the version numbers, e.g. +Then commit this file. (If this new perldelta needs to get cherrypicked +anywhere, this provides a clean base to merge from.) + +For example, assuming 5.10.2: + $ cp -i Porting/perldelta_template.pod pod/perl5102delta.pod $ (edit it) $ git add pod/perl5102delta.pod + $ git commit -m 'create perl5102delta' + +Edit the previous delta file to change the C from C +to C and commit it. For example: + + $ git add pod/perl5101delta.pod + $ git commit -m 'retitle perl5101delta' + +Now you need to update various tables of contents, most of which can be +generated automatically. Edit F: add the new entry, flagged as 'D', and unflag the previous entry from being 'D'; for example: @@ -939,16 +954,13 @@ Manually update references to the perlNNNdelta version in these files: INSTALL README -Edit the previous delta file to change the C from C -to C. - These two lists of files probably aren't exhaustive; do a recursive grep on the previous filename to look for suitable candidates that may have been missed. Finally, commit: - $ git commit -a -m 'create perlXXXdelta' + $ git commit -a -m 'update TOC and perldelta references' At this point you may want to compare the commit with a previous bump to see if they look similar. See commit ca8de22071 for an example of a -- cgit v1.2.1