Any chance of improving these communications? Looks like it might be a lot of work to do, but it would be nice to have it laid out accessibly what changes will be visible to the user and what's under the hood. Thanks.
I agree with Jason, the last commenter: these communications are frustrating as they don't simply list a summary of what significant changes can be noticed by the user, and that's exactly what we need. Please consider creating a short, usable changelist summary. A side-benefit for Google is that more people will be willing to experiment with the different channels. Thank you.
It's funny, I was going to suggest the same thing, and then I see 3 other people feel the same. I understand why it could be considered impractical or unimportant for the browser, especially with the frequent updates (and more-so for beta or dev channel), but ChromeOS is a slightly bigger deal for those supporters among us. Y'know, seeing as how it almost-solely determines the usability of not just some device we spent a few hundred bucks on, but a device that many of oft rely on as our only semi-serious computer...like, y'know, us Chromebook users who leave the house without a second computer.(note: that last bit isn't to imply that ChromeOS is unreliable, or reliable on a patch-to-patch basis, just to point out that there's an "OS" after "Chrome" in some cases. ;) )(note 2: I realize this comment is in response to a Beta Channel update, and it's not so far-fetched to expect users of what's technically an experimental operating system to get their changenotes from an SVN summary, but how about at least for stable-branch? In either case, I can't imagine it would require a noticeable amount of manwork to implement - I bet even most of your interns [you guys have interns, right?] could get the job done in a trivial amount of time...hell, I'd even go so far to say as it'd be a valuable use of their time at that [assuming they're programmers, of course...]. Anyway, I'm starting to ramble now [or this oddly-small comment box is making me feel like I am, anyway], and I think you get the idea, so.. 'nuff said!)YT, YT
Estoy muy en acuerdo con ellos, me parece que deberian de especificar los cambios, ya que el usuario tiene que adivinar cuales son los cambios.
I agree with everyone else. Make these changes and updates easier to read. Tired of seeing the same generic feature enhancements and security updates message. Let me know whats going on with my Chromebook so I can get excited about it and have something to tell my friends and family.
Hey Chrome devs, it sure would be good to have a response, any response, to these comments.Please respond if you are reading them.
Post a Comment