Thank you! We work really hard on the GCP roadmap program, keeping it fully accountable, and pushing against interesting transparency limits.
A public GCP roadmap is also in longer plans but there's a few internal flows we want to improve first. I'm especially trying to reduce the number of sites people need to visit, and want to ultimately see it land in a common place where authenticated users also see the non-public / NDA aspects.
And seconding this advice on access. If you are a GCP customer, your account manager is able to add your account for access. My contact info is in my profile and I can reach your account team if you have difficulties.
Yeah. All Cloud deprecations have a minimum of a year notice, usually as an email, ahead of multiple follow up emails as the year draws close. It's in the terms.
Additionally, you can also get this information in the public release notes https://cloud.google.com/release-notes twice-monthly GCP newsletter, and for G Suite administrators in their news area. "Sigh."
Maybe it is. I feel like this is the narrative on every second cycle since 10.6 (Snow Leopard, to 10.5's Leopard), that "this" is the one where things get more reliable and nature.
> To obtain a library card in any state in the U.S., the applicant must be the person who will ultimately be controlling/using the card, and a significant amount of identifying information must be provided by the person to the state in order to obtain the library card.
This is nonsesne, or at least was here in Sunnyvale California. I walked in with a phone bill. No ID, nothing else. In hindsight it probably could have been anyone's bill, or even a fake.
'Major' is up to personal definition and will distract people here no doubt. Metafiter has been my long-time lighthouse for this kind of gauge, though obviously not as big as its peak.
In the instance of these headphones, the app allows you to adjust the level of active noise cancellation as well as choose which sources can send audio to the headphones. Neither of which are set up to be done directly via the device.
Nah. The number of issues on any project is not an indication of project quality but community activity and imagination for improvements. This is the wrong number to point to if you're trying to make this point.
It is an important question, but Google services which are largely consumer-based and no cost are a very different world from Google Cloud. People get a lot of Internet Cool Guy points these days from falsely conflating the two.
I'm not the to make commitments but our history has been solid, and our deprecation policy is embedded in our terms of service for every Cloud user.
The only product I can remember us deprecating in GCP was Prediction API in favor of the much-preferred Cloud Machine Learning Engine, and with that came communication to every single affected admin and a _year_ before cut-off.
One area I've found helpful is focusing on sources of clarity. With the volume of information/data of all levels of quality becoming so abundant to the point of being overwhelming, and that volume used to influence, the more I can identify the answer to these two points with what is being shoved my way, the better I feel about what I do ultimately select:
- What supposed truth is this information trying to uphold or undermine?
- Is this information trying to make me more or less active on the previous point?
Increasingly I'm getting out of the habit of accepting "I've heard something like this a LOT lately" as a positive sign of influence or motivation toward a next step. Any idiot can buy out the podcast ad inventory to sell their buddy's brain genius pills, it doesn't make consumption wise.
(The poster linked to their own blog post, so maybe they'll add their own opinion to either, rather than summarizing two quotes from David Allen.)
- Release notes: https://cloud.google.com/release-notes
- GCP Blog: https://cloud.google.com/blog/products/gcp