Change order of ops website then notices; additional web pages

Make sure to update the website before announcing since people will go
to the web site expecting the new info.

Update the ci testing pipleine page at wiki.roundup-tracker.org
so it counts commits from current release.

Also update release dates on wikipedia pages for Roundup and issue
tracker comparisons.

Author: rouilj

RELEASE.txt

@@ -168,20 +168,27 @@ Roundup release checklist:
     distributions (if created). Follow the directions for generating
     the gpg asc files and upload the .whl distribution and .whl.asc
     signature files together.
-14. Send doc/announcement.txt to [email protected],
-    [email protected],
-    [email protected], and [email protected].
-14b. Update entry on https://freshcode.club/projects/roundup-tracker
-14c. Update entries for fossies by emailing announcement to
-     [email protected]
-14d. Update entry on https://directory.fsf.org/wiki/Roundup.
-15. Refresh website.
+14. Refresh website.
       website/README.txt
       https://www.roundup-tracker.org/ should state that the stable
       version is the one that you released.
       https://www.roundup-tracker.org/docs.html should also match the
       released version (or at least the major non pre-release
       1.x/2.x version).
+16. Send doc/announcement.txt to [email protected],
+    [email protected],
+    [email protected], and [email protected].
+16b. Update entry on https://freshcode.club/projects/roundup-tracker
+16c. Update entries for fossies by emailing announcement to
+     [email protected]
+16d. Update entry on https://directory.fsf.org/wiki/Roundup.
+17. Change the release version on the GitHub section at
+    https://wiki.roundup-tracker.org/CiTestingEnvironment
+17b. Update release info on wikipedia:
+     https://en.wikipedia.org/wiki/Roundup_(issue_tracker)
+
+     https://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems
+
 
 -------------