OWP Launch bugs & Intent to Ship/Remove

[Jochen Eisinger]

Hey all,

please file OWP launch bugs for features you want to ship (or remove or change)!

OWP launch bugs will trigger a bunch of feature reviews, such as privacy and security reviews, and help the respective teams to keep track of what is going into which milestone.

The "intent to *" templates already contain a field for those bugs, and the API owners will start to block feature launches on the presence of those bugs going forward.

You can file a OWP launch bug by selecting the "OWP Launch Traclomg" template on crbug.com/new

best

-jochen

[Rick Byers]

The OWP launch bug template is completely redundant with the information in the ChromeStatus.com entry.  When a Chromestatus entry exists (i.e. should be for anything non-trivial) can we replace most of the template with a link to the chromestatus entry?  Perhaps the template should be updated to say that?

Rick

[Jochen Eisinger]

Chromestatus doesn't trigger the internal launch tracking process, so no, unless somebody volunteers to hook that up :-)

[Rick Byers]

Oh I'm not suggesting not having the Launch bug - I understand the need for that.

I'm just suggesting that rather than tediously entering the same information twice, the Launch bug can just have a good summary and the body can contain only a link to the chromestatus.com entry for all the details.  Many of these details change over time (support in other browsers etc.) so are better represented in chromestatus than crbug anyway.

For context here is the OWP Launch bug body template:

(See http://www.chromium.org/blink#launch-process for an overview)

Change description:

<1 or 2 sentences here>

Changes to API surface:

<bulleted list here>

Links:

Public standards discussion: <link here>

Support in other browsers:

Internet Explorer:

Firefox:

Safari:

*Make sure to fill in any labels with a -?, including all OSes this change

affects. Feel free to leave other labels at the defaults.

Rick

[Jochen Eisinger]

Oh, I see what you're saying. Yeah, adding the right labels, a sensible subject and a link to chromestatus is enough

[Rick Byers]

Great, thanks.  I tried to update the launch process instructions to capture this, please edit if my wording is sub-optimal.

By the way, it looks like the deprecation instructions don't say anything about OWP launch bugs or chromestatus.  Should they?

Rick

[Jochen Eisinger]

They should - chromestatus also tracks deprecated and removed features

[Philip Jägenstedt]

I have fiddled with the templates so that they all have a "OWP launch tracking bug" section and don't make it optional to include it.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[PhistucK]

On Fri, Jun 5, 2015 at 7:43 PM, Rick Byers <rby...@chromium.org> wrote:

Many of these details change over time (support in other browsers etc.) so are better represented in chromestatus than crbug anyway.

But it is good to have the history of changes (not browser support, but feature details, such as names, extent of support and such) in the bug itself, as comments.​

☆PhistucK