Have a production project on the prior release for regression comparison (Community Wishlist/W300)
Long-term opportunity
Description
Often, the mediawiki software release process occurs and "something breaks". This is often hard to accurately explain the details of, as there is no easy way to check the prior software behavior. Yes, in theory this should be caught in the group0 stage, but there are extremely limited users that are in group 0. Proposing that one project be kept a release cycle behind the primary group. This could be another project (e.g. test3wiki). As these issues are mostly discovered in Wikipedia's, proposing this at least start there.
Assigned focus area
Unassigned
Type of wish
System change
Affected users
users, tech ambassadors
Other details
Voting