797
edits
Release Management/Rapid Betas: Difference between revisions
Jump to navigation
Jump to search
→Questions& Responses
| Line 126: | Line 126: | ||
= Product Marketing & PR = | = Product Marketing & PR = | ||
'''Update''' - Grace & Laura discussed; EJ added input; questions and blockers below. | '''Update''' - Grace & Laura discussed; EJ added input; questions and blockers below. | ||
== Questions& Responses == | == Questions & Responses == | ||
* This will have an impact on how we could deploy a What's New Page which we've planning to do for sometime. We will likely still be able to, but we'll have to coordinate much closer on when and how those pages are turned off and on. What would be the details of getting a paged turned on or off? | * This will have an impact on how we could deploy a What's New Page which we've planning to do for sometime. We will likely still be able to, but we'll have to coordinate much closer on when and how those pages are turned off and on. What would be the details of getting a paged turned on or off? | ||
* How will this effect release notes? Will we update them every day? Once a week? | ** No clear answer on this. This is not a blocker, but something to keep in mind for the future to find a solution. | ||
* How will this effect release notes? Will we update them every day? Once a week? | |||
** Will keep doing release notes the way we do Aurora--stand them up with initial release and make minor changes as needed; don't think we will see major changes between first release and end of the cycle. | |||
* How will this effect how we track comments/feedback on Input? | * How will this effect how we track comments/feedback on Input? | ||
** Yes, it will. Will need a way to correlate comments to buildIDs. | |||
* Will this effect how we track ADUs/ADIs with metrics tools? | * Will this effect how we track ADUs/ADIs with metrics tools? | ||
** Yes, Alex is filing a bug. | |||
* How will users be alerted to the updates? Will it cause update fatigue? | * How will users be alerted to the updates? Will it cause update fatigue? | ||
** No because this will only be implemented after silent updates. | |||
* Is this the new way of doing things or a short term thing we are testing? | * Is this the new way of doing things or a short term thing we are testing? | ||
** Its the plan for the foreseeable future, but may be changed depending on resources, needs, etc. | |||
* Does this mean new features can land in beta? | * Does this mean new features can land in beta? | ||
** It makes it less risky to land features, but any feature additions will be discussed in depth before landing; don't think this will cause an increase in the landing of new features. | |||
* Do we have to update our communications around what to expect for each channel? | * Do we have to update our communications around what to expect for each channel? | ||
** I don't think it does, apart from a general blog post announcing the change. | |||
* Will this change the release timeline? | * Will this change the release timeline? | ||
** No, this shouldn't effect release timeline at all. | |||
== Blockers == | == Blockers == | ||