[Lucene-java Wiki] Update of "JenkinsReleaseBuilds" by SteveRowe

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The "JenkinsReleaseBuilds" page has been changed by SteveRowe:
https://wiki.apache.org/lucene-java/JenkinsReleaseBuilds?action=diff&rev1=9&rev2=10

Comment:
Remove info about downstream jobs (no longer applicable)

     * Copy the job (Jenkins|New Item|Copy existing job), and name the new job by substituting the release version for the version in the copied job's name, e.g. s/6.x/6.0/.
     * It's a good practice to create the job as initially disabled (check the checkbox next to "'''Disable Build (No new builds will be executed until the project is re-enabled.)'''"), and then enable them all at once after you've finished creating them.
     * Switch the '''Branch Specifier''' under '''Branches to Build''' in the '''Source Code Management''' section to point to the release branch, e.g. {{{*/branch_6x}}} -> {{{*/branch_6_0}}}
-    * If this job kicks off another job (look under Post-build Actions|Build other projects), make sure you rename the job to kick off (Projects to build) by substituting the release version for the version in the job's name, e.g. s/6.x/6.0/.  Currently, {{{Lucene-Solr-NightlyTests-<version>}}} kicks off {{{Lucene-Artifacts-<version>}}}, and {{{Lucene-Artifacts-<version>}}} kicks off {{{Solr-Artifacts-<version>}}}.
-    * Except for the jobs triggered by other jobs (see above), all jobs are scheduled to run periodically.  No changes should be required on the cloned jobs to handle this properly.
+    * All jobs are scheduled to run periodically.  No changes should be required on the cloned jobs to handle this properly.
   * If you created the new jobs in the disabled state, enable them all now.