On Wed 08 Mar 2006 at 11:42AM, Dan Price wrote:
On Wed 08 Mar 2006 at 10:49AM, Karyn Ritter wrote:
I'll figure out where to put the definitions. This the real status that
is in Bugster, so we need to document it anyway
So, I wonder if we could use Perl's WWW::Mechanize [1] or something
On 3/8/06, Karyn Ritter Karyn.Ritter at sun.com wrote:
snip
Would something like the table I've just created at
http://www.opensolaris.org/os/bug_reports/oss_bite_size/ help? I need to
Very nice view of what is out there.
Please provide comments ideas about this and other ways we can help
On Mon, Mar 06, 2006 at 02:40:39PM -0700, Sanjay Nadkarni wrote:
I will back this up from the request sponser POV. In my case an RPE engineer
had already fixed the bug and putback into Nevada. However we don't require
people to update the fixed in bugster.
People have suggested that we
On Wed, Mar 08, 2006 at 03:06:46PM -0800, Danek Duvall wrote:
On Mon, Mar 06, 2006 at 02:40:39PM -0700, Sanjay Nadkarni wrote:
I will back this up from the request sponser POV. In my case an RPE
engineer
had already fixed the bug and putback into Nevada. However we don't
require
Danek Duvall wrote:
On Mon, Mar 06, 2006 at 02:40:39PM -0700, Sanjay Nadkarni wrote:
I will back this up from the request sponser POV. In my case an RPE
engineer
had already fixed the bug and putback into Nevada. However we don't require
people to update the fixed in bugster.
People
Alan Coopersmith wrote:
James Carlson wrote:
Having engineers rather than gatekeepers marking bugs as
integrated, as Alan describes for non-ON gates, seems broken to
me.
Well, it is admittedly for gates with no gatekeepers. When you have
a fraction of the developers ON does, you get
Joel Buckley wrote:
I manage a consolidation with a total of 2 developers. Even with this
size the gatekeeper role is intact. I would suggest the wording be
explicitly stated for the gatekeeper. Then describe the role the
gatekeeper conducts as part of the product release process.
Perhaps
On Mon, 6 Mar 2006, Jim Grisanzio wrote:
* For those who are thinking about contributing code, what can we do to
help you get started? Would more oss-bite-size bugs help?
More oss-bite-size would be nice. I also have a couple of suggestions for
the bug list. One is to make sure the bug
On Mon, Mar 06, 2006 at 02:47:26PM -0800, Alan Coopersmith wrote:
That seems broken, but I suppose that's my non-ON point of view, coming
from consolidations where the engineer marks the bug fix available when
they submit the fix for code review and integrated when they putback to
the master
Sanjay ... we don't require people to update the fixed in bugster. The
Sanjay fixed, committed and integrated fields get updated only when the build
Sanjay closes.
Alan That seems broken, but I suppose that's my non-ON point of view, coming
Alan from consolidations where the engineer marks the
10 matches
Mail list logo
