I hope this serves to remind everyone that we need to keep the tree in
a state where it is always shippable.
If you're going to implement only a portion of a feature, make sure
it's not visible to the user until it's fully operational. Even if you
intend to flip the rest on in a few hours, something may go awry (tree
closures, concerns raised about your cl, a new episode of My Antonio
on VH1, etc) that prevents you from landing for a day or more.
On Sat, Sep 19, 2009 at 2:37 PM, Nico Weber tha...@chromium.org wrote:
By the way: After resizing the window, you can hit cmd-shift-b twice
to move the bar back to the bottom of the window.
On Sat, Sep 19, 2009 at 11:01 AM, Nico Weber tha...@chromium.org wrote:
Hi,
wondering why there's a grey, useless bar at the bottom of the latest
mac dev release? It is not intentional, and is my fault – sorry. It
will be gone again in next week's dev release. It was only active on
trunk for a few hours, but this week's dev release was cut in that
interval.
If you see a bug filed for that, mark it as dupe of 19073 and write
something like
Bug 19073 landed prematurely and has been backed out.
Unfortunately, the 211 build
came from the tiny window when it was checked in.
Nico
--
Mike Pinkerton
Mac Weenie
pinker...@google.com
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---
