| That would fall into the bucket of early reviews. If the early reviews template requires too much time, happy to optimize some of the inefficiencies.
Early review also shouldn't require multiple stakeholder signal, although we haven't applied that rule consistently. I'm working on a proposal to make this (and other inconsistencies in how the TAG responds to reviews) more consistent. Sangwhan On Oct 20, 2023, at 7:02, Alex Russell <slightly...@chromium.org> wrote:
TAG review of explainers before WG agreement is optimal and recommended! what's your advice on going to TAG with respect to getting agreement in the WG? I've got a couple of spec changes now that I really would like TAG to review early, but they consist of an explainer + PR because the WG doesn't have agreement to merge yet.
Harald
+1
The TAG has introduced (~year ago, I think?) an "Early Design Review", which is a lot more lightweight than the "Specification Review".
If you haven't gone through this part of the process before, I'd encourage you to try again and look into using the TAG for "Early Design Reviews" somewhere between your I2P and you kicking off a Devtrial.
Sam
Hey all,
A frequent occurrence in recent reviews have been sizeable features arriving at Intent-to-Ship with no effort made in previous intents to ask the TAG for advice and no reason given for avoiding this part of the processes.
This slows down launches while we pause consideration of an intent to give the filer time to consult the TAG and wait O(weeks) for a response.
You should expect delays of this sort of you do not file a request for feedback for TAG review at or near I2P-time, preferably as soon as you have an Explainer that holds together.
If you have questions about of and when to ask the TAG for feedback, don't hesitate to ask me or other current/ex-TAG members privately for feedback.
Best,
Alex
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA44PQhmudMCTwbuSywafnwxiY6mU2e34nHzTEFdqGrHMMjPFg%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALdEk-wW9wErZQMGj7QhrSeOFJL25MzJ6wdyeH9k%3DXZMnYUJzg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA44PQgxk3X7HRhCevHyMnye2vSSb%2Bu%2BymBZkHVoN0BLVgRx8Q%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4E6EBB18-43B9-4A77-8D49-00E6E643B6CC%40chromium.org.
|
