On Sep 7, 7:45 pm, Dylan Bennett <[EMAIL PROTECTED]> wrote:
> I aggregated the changelog's from the buildbot snapshots and listed
> them out. Maybe it will be useful until Google releases their own
> list?
>
> http://mboffin.com/post.aspx?id=2268
>
> --Dylan
Please remove that post, it might confuse people.
You're confusing Chromium's continuous builds with Google Chrome. We
don't release Google Chrome directly from the tip of the source code
tree becuase that's where active development happens (and things there
are likely to be half baked and buggy at any arbitrary time). The tip
of tree (TOT) is currently working on the build 151 development cycle,
and that's what the log you posted reflects.
However, the latest update to Google Chrome is 149.29. It was built
from a revision of the source code much older than 151 with just a few
selected changes added to it.
I really admire your enthusiasm and initiative to plug an obvious
hole. Having generated build change logs many times myself, I can tell
that you spent a fair amount of time looking at the svn logs.
We're working on the change list for the current version of Google
Chrome -- 149.29. The delay is not really excusable, and I hope we'll
fix our release process so this doesn't happen again.
Thanks,
Mark Larson
Google Chrome Program Manager
>
> On Sep 7, 11:28 am, [EMAIL PROTECTED] wrote:
>
> > I have searched a lot of places to find the release notes for the
> > latest version (0.2.149.27 to 0.2.149.29) and I can't seem to find the
> > changelog. Does anybody know where it is, or if there even is one?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
