RMG: Move merge dev perldeltas section behind a checklist guard

Author: thibaultduponchelle

Porting/release_managers_guide.pod

@@ -467,6 +467,20 @@ When doing a MAINT release, check that perlgov lists the I<current>
 Perl Steering Council and Core Team members, in case they have changed
 since the corresponding stable release has been shipped.
 
+=for checklist skip MAINT BLEAD-POINT RC
+
+=head3 Merge BLEAD-POINT perldeltas
+
+All perldeltas from the 5.X series must be
+merged into F<pod/perldelta.pod>. The process starts with
+
+    ./perl -Ilib Porting/merge-deltas.pl
+
+The resulting F<pod/perldelta.pod> will need to be edited.  In particular,
+lists will need to be merged.  Sections which were describe changes which
+were reverted will need to be removed.  Some items may benefit from being
+merged into a new summary.
+
 =head3 Update perldelta
 
 Get perldelta in a mostly finished state.
@@ -480,16 +494,6 @@ release process.
 Read F<Porting/how_to_write_a_perldelta.pod>, and try to make sure that
 every section it lists is, if necessary, populated and complete.
 
-In the case of a BLEAD-FINAL, all perldeltas from the 5.X series must be
-merged into F<pod/perldelta.pod>. The process starts with
-
-    ./perl -Ilib Porting/merge-deltas.pl
-
-The resulting F<pod/perldelta.pod> will need to be edited.  In particular,
-lists will need to be merged.  Sections which were describe changes which
-were reverted will need to be removed.  Some items may benefit from being
-merged into a new summary.
-
 You won't be able to automatically fill in the "Updated Modules" section until
 after L<Module::CoreList> is updated (as described below in
 L</"Update Module::CoreList">).