Porting/release_managers_guide.pod: about smokers and BLEAD

Note that you don't have to wait for smokers for a BLEAD release,
because there simply isn't time.

diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index b3c765d..dfffe17 100644 (file)
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -781,6 +781,12 @@ based on (or at least the last commit of any consequence).
 Then check that the smoke tests pass (particularly on Win32). If not, go
 back and fix things.
 
+Note that for I<BLEAD> releases this may not be practical. It takes a
+long time for the smokers to catch up, especially the Win32
+smokers. This is why we have a RC cycle for I<MAINT> releases, but for
+I<BLEAD> releases sometimes the best you can do is to plead with
+people on IRC to test stuff on their platforms, fire away, and then
+hope for the best.
 
 =item *