new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

GitHub Primer · all subjects

feature-onboarding/lifecycle-labels

4 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Feature lifecycle stages

There are currently 4 main lifecycles: Private Preview (formerly Alpha, Private Beta, Staff), Public Preview (formerly Limited Public Beta, Public Beta), General Availability (GA), and Closing Down. Private Preview features are not publicly announced and support is handled by the product and engineering team with no SLAs. Public Preview features are publicly announced but customers should not yet take production dependencies on the service with no SLAs, and support is handled by product and engineering teams with possible Support team involvement with VP approval. General Availability features are available to ALL GHEC Customers, SLAs apply where applicable, and support is provided. The Technical Preview label may sometimes be used by the Next team for experiments and research projects.

Feature lifecycle terminology and color

It is important to stick to the correct terminology and label color when referring to a lifecycle. The terms Alpha and Beta are no longer used to identify stages. Instead, Private Preview and Public Preview are used in the UI. Use the correct label and link color when referring to lifecycle stages.

Feature lifecycle feedback and deprecation

Gathering feedback through a discussion is recommended to enable seamless follow-up with the user. This discussion should specify the changes made, providing clarity to the user about what's new. In case of deprecating a feature, provide additional information through documentation. Features that were never promoted beyond the Private Preview lifecycle do not need to go through a deprecation lifecycle.

Feature lifecycle labels usage

Consider using standalone labels for features that appear in a user's current view but may navigate away from their current page to fully engage with the feature. If the label is not part of a navigational item, include a 'Give feedback' or 'Learn more' link to collect information on how the changes are perceived by the user. Labels provide a softer way to accentuate new features without derailing users from their primary task.

Give your agent this brain