Bugzilla

(In reply to :Gijs (he/him) from comment #38)
> (In reply to Tom Prince [:tomprince] from comment #37)
> > Would it make sense to enable this by default on non-nightly branches?
> 
> I don't think so; it'd mean that if the update defines a what's new page for any beta/release build, we will show it even for security dot-releases and/or bN to bN+1 updates -- unless we permanently alter all our server-side logic to never include a what's new page for such updates (assuming we can do that for any/all such updates that aren't major version updates).

That code live in-tree ([here](https://searchfox.org/mozilla-central/source/browser/config/whats_new_page.yml)) and is *already* configured so that doesn't show the WNP for dot-releases or bN->bN+1 updates. That is, the server-side logic is already configured to support this code running on releases.

(In reply to :Gijs (he/him) from comment #38)
> (In reply to Tom Prince [:tomprince] from comment #37)
> > Would it make sense to enable this by default on non-nightly branches?
> 
> I don't think so; it'd mean that if the update defines a what's new page for any beta/release build, we will show it even for security dot-releases and/or bN to bN+1 updates -- unless we permanently alter all our server-side logic to never include a what's new page for such updates (assuming we can do that for any/all such updates that aren't major version updates).

That code lives in-tree ([here](https://searchfox.org/mozilla-central/source/browser/config/whats_new_page.yml)) and is *already* configured so that doesn't show the WNP for dot-releases or bN->bN+1 updates. That is, the server-side logic is already configured to support this code running on releases.