The release has lots of fixes tracked by bug 637452, and no known regressions. The rsync-verify USE flag is now in package.use.stable.mask due to bug 649276 and bug 647964.
(In reply to Zac Medico from comment #0) > The release has lots of fixes tracked by bug 637452, and no known > regressions. Tracker is actually bug 645194.
An automated check of this bug failed - repoman reported dependency errors (2 lines truncated): > dependency.bad sys-apps/portage/portage-2.3.24-r1.ebuild: RDEPEND: alpha(default/linux/alpha/13.0) ['>=app-portage/gemato-10'] > dependency.bad sys-apps/portage/portage-2.3.24-r1.ebuild: RDEPEND: alpha(default/linux/alpha/13.0/desktop) ['>=app-portage/gemato-10'] > dependency.bad sys-apps/portage/portage-2.3.24-r1.ebuild: RDEPEND: alpha(default/linux/alpha/13.0/desktop/gnome) ['>=app-portage/gemato-10']
An automated check of this bug succeeded - the previous repoman errors are now resolved.
You don't stabilize on an arch which had no ~arch keyword. That defeats the purpose of not committing straight to stable.
ia64 stable
commit 0fe5fba2f21f24485febdbefe96313584e2dda80 Author: Rolf Eike Beer <eike@sf-mail.de> Date: Sat Mar 10 13:13:42 2018 +0100 sys-apps/portage: stable 2.3.24-r1 for sparc, bug #650060
x86 stable
hppa stable
amd64 stable
ppc/ppc64 stable
arm stable
alpha stable
See bug 657058 for next stable.