We're going to reorganize the labels in the bug tracker to make it easier
for release managers to accurately triage more focused areas. This is a
follow up to adding the Feature- labels for tracking specific features.
For most of you, this will have little impact. Some of the top-level Area-
The feature freeze for 4.0 Stable is end of day today (Friday, 13 Nov). I've
had a few questions about branching, either from people who want to delay
committing crazy patches or people who want to make sure their feature lands
before we branch.
In a nutshell, we're going to branch Monday morning
On Tue, Nov 10, 2009 at 08:14, mrossetti mrosse...@chromium.org wrote:
I've updated http://crbug.com/25959 with some comments.
The suggestion was made to exclude the entire profile directory as a
short-term solution, but that would mean not backing up the bookmarks
and cookies. So for the
We need to change the address used by the issue tracker from '
codesite-nore...@google.com' to 'chrom...@googlecode.com'.
I'll be making this change immediately. Your mail filters might be affected.
--Mark
--~--~-~--~~~---~--~~
Chromium Developers mailing list:
We're now publishing the DEPS for release candidate builds. See
http://src.chromium.org/viewvc/chrome/releases/3.0.195.27/
http://src.chromium.org/viewvc/chrome/releases/4.0.222.1/
The DEPS file should be good enough to build the release, though I found I
had to manually set
You can use the form issue project:bugid in bug descriptions to
autolink to bugs in other code.google.com projects like v8, skia, googleurl,
etc.
As of today, this form is supported for Duplicate and Blocked on. So, for
example, I marked V8's http://code.google.com/p/v8/issues/detail?id=19 as a
http://dev.chromium.org/developers/coding-style
There's a section on Subversion properties that looks like it predates GYP.
It says to set *.sln = svn:eol-style=native when I would expect it to be in
global-ignores.
Can someone with a good idea of what the defaults should be update this
page?
We're in the process of changing a few things about how security issues are
handled.
*1. Security bugs are restricted to members of the 'Security Team' by
default.*
We will limit access to security issues to a smaller set of people. This is
consistent with how other projects (WebKit, Mozilla for
Just so we don't waste Darin's time on administering code.google.com when he
could be doing Yet Another Code Review...
Please send requests for issue tracker changes --like getting automatically
CC'd for a given label-- to jon@ and laforge@ (chromium.org).
--Mark
On Mon, Aug 17, 2009 at 11:36,
Yes, I think we can add something so each channel has a persistent URL. I'll
discuss with Aaron offline.
On Sat, Aug 8, 2009 at 00:17, Darin Fisher da...@chromium.org wrote:
On Fri, Aug 7, 2009 at 11:59 PM, Aaron Boodman a...@chromium.org wrote:
Ok, sorry I got defensive. Short answer is we
On Wed, Jul 22, 2009 at 14:02, Peter Kasting pkast...@google.com wrote:
On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow jor...@chromium.org wrote:
Here comes the bike shedding
Yes, Evan already concluded that was where we were.
RELEASE_NOTES=
I thought the conclusion was that people
On Wed, Jul 22, 2009 at 20:27, Dan Kegel d...@kegel.com wrote:
Stop me if you've heard this one before.
Today, a new directory was added to the source tree, and shortly
thereafter was reverted.
Should have been no problem, but... because the new directory
contained a gyp file, a file was
On Wed, Jul 22, 2009 at 21:26, Dan Kegel d...@kegel.com wrote:
On Thu, Jul 23, 2009 at 4:15 AM, Mark Larson (Google)m...@chromium.org
wrote:
Should have been no problem, but... because the new directory
contained a gyp file, a file was generated in that directory,
and svn couldn't delete
On Fri, Jul 17, 2009 at 10:48, Aaron Boodman a...@chromium.org wrote:
I propose we add a new tag to changelist descriptions:
RELEASE_NOTE=description of something interesting that users would
like to know happened in this build
It would be up to the developer to decide whether something
The chromium-reviews emailing list has been blacklisted (for spam
apparently).
No review email is going out. We're working to get the list restored, but
don't have an ETA at this point.
In the meantime, you'll need to ping people directly to let them know about
pending reviews and comments.
We're working on adding more trybot capacity (3x for Mac). Additional Macs
should come online in the next week or so, which will reduce the try
latency. Right now, we're really underpowered.
Yoda would be happy that there is no try. Developers, not so much.
--Mark
On Thu, Jun 25, 2009 at 18:39,
See http://code.google.com/p/chromium/issues/detail?id=15286
http://code.google.com/p/chromium/issues/detail?id=15286This seems to be a
regression from (or a latent bug uncovered by)
http://src.chromium.org/viewvc/chrome?view=revrevision=19183
Jungshik is looking into it.
On Wed, Jun 24, 2009 at
I plan to do a maintenance update to 172 on the Stable channel next month.
If you know of bug fixes that should be included, please add the *Merge-Stable
label* to the bug. I'll review fixes and pick up many as I can without
adding too much risk.
Thanks,
Mark
#1, make sure you have a bug open and a design document
(exampleshttp://dev.chromium.org/developers/design-documents).
Nothing's worse than going off on a long-lived feature expedition and then
returning to trunk to find out people don't want the feature or want some
other design.
#2, work on
This is happening on a new Google Chrome Linux builder on the 'experimental'
waterfall:
http://build.chromium.org/buildbot/waterfall.fyi/waterfall?branch=builder=Google+Chrome+XPbuilder=Google+Chrome+Linuxreload=60
The linux compile fails here:
Linking
:
On Wed, Jun 17, 2009 at 2:33 PM, Mark Larson (Google)m...@chromium.org
wrote:
This is happening on a new Google Chrome Linux builder on the
'experimental'
waterfall:
http://build.chromium.org/buildbot/waterfall.fyi/waterfall?branch=builder=Google+Chrome+XPbuilder=Google+Chrome+Linuxreload
Yoav, I'm glad to hear you're interested in helping make Chromium better!
The best way to get started is to get specific broken behaviors documented
as bugs and then work on fixing the bugs.
We already have a lot on file:
http://code.google.com/p/chromium/issues/list?can=2q=label:RTL
On Fri, May 29, 2009 at 16:16, Evan Stade est...@chromium.org wrote:
On Fri, May 29, 2009 at 4:07 PM, Mohamed Mansour
m0.interact...@gmail.com wrote:
Let me clarify. Try typing this:
Hasn't the dog ate his food.
hopefully we'll soon have grammar checking as well :)
I hope the grammar
...these issues are filed as bugs so we can fix them, right?
On Fri, May 29, 2009 at 22:23, Peter Kasting pkast...@chromium.org wrote:
On Fri, May 29, 2009 at 7:45 PM, Evan Stade est...@chromium.org wrote:
I'll also take this opportunity to complain that the dangerous
downloads dialog
See
http://dev.chromium.org/developers/design-documents/multi-process-architecture
and
http://dev.chromium.org/developers/design-documents/process-models
http://dev.chromium.org/developers/design-documents/process-modelsThese
are on http://dev.chromium.org/ by clicking on For Developers and then
Just so it's clear to me... why do we need a History menu?
There's a link to history from the wrench menu/Ctrl+H and also from the New
Tab page.
The
back button provides at least 12 entries from the back history for the
current tab. That seems more than
adequate for the 'jump back a few steps in
I'm working on documenting the normal schedule for release milestones and
how we track that in the bug tracker.
I still have some issues to work out around when a particular feature is
ready and qualified for Beta and Stable channel releases.
For the Dev channel, however, we have a
On Tue, May 12, 2009 at 07:48, Marc-Antoine Ruel mar...@chromium.orgwrote:
On Tue, May 12, 2009 at 3:44 AM, Mark Larson (Google) m...@chromium.org
wrote:
The release manager for the week cuts a dev channel build Monday morning
(Pacific) from the LKGR at that time.
To be sure, uou
On Wed, Apr 29, 2009 at 14:05, Mike Belshe mbel...@google.com wrote:
We're still using the test-shell to run the LayoutTests.I just fixed a
bug, wrote a layout test, and then realized how dumb I was because the code
I was testing was only in Chrome, and not in the test_shell.
I think
If you don't have a 172 branch checked out, you can stop reading.
I updated the V8 dependency to use branches/1.1 instead of trunk. You need
to delete src/v8 and gclient sync to get your working copy to switch to the
branch.
--Mark
--~--~-~--~~~---~--~~
Chromium
All changelists should have
TEST=
BUG=
if at all feasible.
Why?
TEST= will ensure that testers get the information they need to cover your
change. What needs to be tested is not always obvious from the CL
description. Sometimes a change in base/ can impact the installer or
downloads. Help
I totally agree. Keep using the spreadsheet as long as it helps the team
make progress and the problem is basically engineer-to-engineer
coordination. As I said, I trust your judgment.
Once we start doing regular Mac and Linux releases, we'll want to use the
bug tracker because a spreadsheet won't
(rafaelw, this isn't personal. It's just the most recent example.)
src/chrome/browser/extensions/extension_tabs_module.cc contains this code at
line 229:
229 int new_index;
230 DCHECK(args-GetInteger(Lindex, new_index));
231 if (new_index 0) {
232DCHECK(false);
233return false;
234 }
The issue tracker at code.google.com/p/chromium may be inaccessible or slow
to respond for the next few hours.
Engineers are working on the issue now, so just be patient. It's a good
chance to ignore bugs for a while :)
--Mark
--~--~-~--~~~---~--~~
Chromium
And it's back already, faster than I expected. Pardon the spam.
On Fri, Apr 10, 2009 at 18:31, Mark Larson (Google) m...@chromium.orgwrote:
The issue tracker at code.google.com/p/chromium may be inaccessible or
slow to respond for the next few hours.
Engineers are working on the issue now, so
On Thu, Apr 2, 2009 at 09:10, Steven Knight s...@chromium.org wrote:
Excellent idea re: qual script. What I'd like to do is turn these items
into sanity-check tests for a buildbot slave that specifically tests and
times issues about the build itself: build time stats, size of dependency
This is awesome. Thanks.
On Tue, Mar 31, 2009 at 12:21, Patrick Johnson patr...@chromium.org wrote:
SunSpider and V8 Benchmark Suite performance is now tracked on the Chromium
Buildbot.
Graphs are available on the performance overview page at:
I don't know how big these fonts are (download size) and I have a terrible
sense of font quality.
I do know that I want to reduce download size.
I'd be all for making some or all of these fonts available, but not as the
defaults. We could host them on our download servers and download them in
the
On Fri, Mar 13, 2009 at 15:01, Darin Fisher da...@chromium.org wrote:
Are we only talking about regressions since 1.0? How many tests are
we talking about?
I agree we should set a baseline and not tolerate regressions from here
forward.
The latter question is the really important one to
Mohamed,
I'm glad to see your interest in tackling this problem.
Unfortunately, that data is collected under an agreement between the user
and Google, so we cannot share the dumps. It's OK to share the stack traces,
which have no personally identifying information, but I'm not sure we can
even
Can we disable them for Google Chrome builds, and leave them on for
Chromium?
We don't currently have an archive of debug builds, but we do have that for
Chromium release builds.
--Mark
On Mon, Mar 2, 2009 at 16:16, John Abd-El-Malek j...@chromium.org wrote:
I was looking at the second top
To aid people who are debugging or porting fixes to various releases, I've
created a release branch representing the current state of each channel:
View: http://src.chromium.org/viewvc/chrome/branches/
release-stable/
release-beta/
release-dev/
As chrome_official_branch is really just a
On Thu, Jan 15, 2009 at 11:08, Jon j...@chromium.org wrote:
*Report for 2009-1-14*
With a single check-in from Finnur we got a huge boost toward our goal of
resolving all the layout test failures! If you would like to try your hand
at fixing a layout test you can preview the 10 minute video
On Wed, Jan 7, 2009 at 17:28, Brad b...@chromium.org wrote:
We have an issue with a site wanting to remain in app mode. At the
time being there is no method to open a new window in that mode from
the page (no Window.Open) and they use a multi-document interface.
The work around would be to
I'm working on release notes for 155. The big addition in 155 (vs the 154
code we've been releasing) is the WebKit update.
What have we gained since we started merging to WebKit's trunk?
So far, I've got
-- full page zoom
-- autoscroll
-- CSS gradients
-- CSS canvas drawing
-- (partly)
On Fri, Dec 19, 2008 at 13:01, Jaff jaffe.m...@gmail.com wrote:
Well, this is too strange. It would seem as if some other file-system
mechanism is cacheing
data. I created a new directory and attempted a fresh checkout, and it
crashes/halts in exactly the same place. Complains about src/
On Tue, Dec 16, 2008 at 07:20, Marshall Greenblatt
magreenbl...@gmail.comwrote:
What is chromium's usage plan for /trunk? It seems that recent beta and
release builds of chrome are coming off of /branches/chrome_official_branch
-- is there a process in place to synchronize
Google employees: in case you're not paying attention, this thread is
public on chromium-dev.
I want to do a Dev channel release from the trunk soon.
I know there are a lot of issues with the current trunk because it hasn't
had the same test exposure or release pressure as the 154 branch.
I
In light of the conversation earlier this week about Issues Assigned to Me
on the issue tracker. There's a fix in, and it should go live next week (or
so).
--Mark
-- Forwarded message --
From: [EMAIL PROTECTED]
Date: Fri, Dec 5, 2008 at 14:05
Subject: Issue 1934 in support: Only
I've filed an issue with code.google.com:
http://code.google.com/p/support/issues/detail?id=1934
Please star that to let the c.g.c team know how many people are interested
in changing the default.
--Mark
On Thu, Dec 4, 2008 at 08:15, Finnur Thorarinsson [EMAIL PROTECTED]wrote:
You have bugs
2008/12/3 MatÃas [EMAIL PROTECTED]
Hi,
I've noticed that since yesterday, Chromium builds have a working
checking for updates in the about window. I'm wondering how is this
supposed to work, since It doesn't seems to correctly detect new
builds.
I'm currently updating Chromium builds with
We have posted guidelines for becoming a committer here:
http://dev.chromium.org/getting-involved/become-a-committer
We have a number of active hackers making great contributions. We want to
encourage more of that. Becoming a committer makes it easier to keep helping
by giving you the power to
On Fri, Nov 28, 2008 at 10:38, Dean McNamee [EMAIL PROTECTED] wrote:
I'm working on Linux layout tests. We're at about ~85% passing right
now, but I know we still have a lot of problems.
I've recently been running into places where I'm trying to fix
problems, but the Windows layout test is
On Sat, Nov 22, 2008 at 14:54, Daniel [EMAIL PROTECTED] wrote:
Does test_shell use V8 or JavaScriptCore?
By default, V8.
On Nov 22, 1:29 pm, Peter Kasting [EMAIL PROTECTED] wrote:
On Sat, Nov 22, 2008 at 11:17 AM, Daniel [EMAIL PROTECTED] wrote:
Basically, I'd like to create a build
We're about to land an update to our WebKit code that contains about 4
months worth of changes. This will make the tree unreleasable. We need to
get the tree healthy again so that we can get back to releasing new stuff to
users.
Until we resolve all of the post-WebKit-merge issues, nothing's
send them directly to me (so I can compile
the FAQ).
Thanks,
Mark Larson
Google Chrome Program Manager
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Chromium-dev group.
To post to this group, send email to chromium-dev
56 matches
Mail list logo
