As part of the bookmarks being turned into "saves" change, the badges associated with bookmarked questions are being updated to reflect the rename, as well as new badges being added for saved answers. The "saves" features have not been released yet, though.

However, as noted in chat, the wording for the "Favorite Question" badges has already been changed, and the new answer versions of these badges are already live in the badges page:

A silver badge named "Favorite Answer" and a gold badge named "Stellar Answer" in the badge list. Neither badge has been earned by anyone.

Since the saves feature changes have not yet been implemented, the badges probably shouldn't be updated or live until the saves feature is actually released. It's just liable to cause confusion by being changed early.


1 Answer 1


Thanks for bringing this to our attention. This was a mistake on our part while we were conducting internal testing. The new Favorite Answer and Stellar Answer badges have been hidden for now.

The badge descriptions for Favorite Question and Favorite Answer still show the “saved” wording due to them being cached. We apologize for any confusion caused. When we are ready to launch, we will communicate and update the original Meta post.

I've updated the status to .

  • 3
    I am really curious, how can "internal testing" cause changes in production? Are those two environments not totally separate? Unless you perform tests on production, which IMHO is pretty bad practice, but hey, that's off topic here. Sep 16, 2022 at 16:34
  • 2
    The environments are separate. Features are tested in a dev environment before they are deployed to production. Once deployed, they can be tied behind a site setting until they are ready for launch. We had several site settings for this feature. When we enabled one of them for internal testing, it made certain changes visible on the site.
    – tanj92 Staff
    Sep 16, 2022 at 16:56
  • 3
    @ShadowTheKidWizard I don't know whether it's helpful but we have two ways to test things "internally" - we can test on our dev environment, which requires access to the dev site or we can ship things to public but only make them available/visible to certain user types - or even specific user IDs. It gives us a chance to see the integrations on the live site. It's how we test Winter Bash every year. It's similar to how mods only have mod tools and devs only have access to certain dev pages... there's even CM-specific pages.
    – Catija
    Sep 16, 2022 at 17:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .