John Levon writes:
I really wish people would just remove themselves as RE when they're not doing
anything, I find it really annoying. I bet there's a number of bugs that
actually aren't getting fixed due to old RE entries.
There's no way to tell. The standing rule I've heard is that if you
OK, I've updated the table at
http://www.opensolaris.org/os/bug_reports/oss_bite_size/ . Some notes:
* This page only contains oss-bite-size bugs that might be available
for the community to work on: there is a link to the fixed
oss-bite-size bugs.
* I was planning to use the
On Tue, Apr 11, 2006 at 02:43:47PM -0700, Karyn Ritter wrote:
OK, I've updated the table at
http://www.opensolaris.org/os/bug_reports/oss_bite_size/ . Some notes:
It doesn't seem useful to me to split out Accepted bugs. The accepted state
doesn't really mean very much at all (I've even seen
I've uploaded a new table to try and address these issues. Please let me
know what you think. Some comments:
* Would it be better to have a table with oss-bite-size bugs that
might be available to work on with a link to others that aren't?
Rather than everything in one table?
* I'm
On 3/8/06, Karyn Ritter [EMAIL PROTECTED] 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 make
the
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
Mike Gerdts wrote:
1) Presumably a responsible engineer means that something is
happening.
Not necessarily - I'm currently the responsible engineer in the bug db for 142
bugs RFE's, some of which have been assigned to me for 5 years or more.
Being human and only having 24 hours in a day,
Bill,
Bill Rushmore wrote:
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.
On Wed, 8 Mar 2006, Karyn Ritter wrote:
Would something like the table I've just created at
http://www.opensolaris.org/os/bug_reports/oss_bite_size/ help? I need to
work out the answers to many additional questions surrounding this table
-- the least of which is how often I can reasonably
I'll figure out where to put the definitions. This the real status that
is in Bugster, so we need to document it anyway
Thanks,
Karyn
Bill Rushmore wrote:
On Wed, 8 Mar 2006, Karyn Ritter wrote:
Would something like the table I've just created at
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
equivalent to automate the updating of pages.
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 have
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
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
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
Keith M Wesolowski writes:
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
On Mon, Mar 06, 2006 at 02:47:26PM -0800, Alan Coopersmith wrote:
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. The
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 by with a fraction of the
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. The fixed,
committed and integrated fields get updated only when the build closes.
So during
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 gate. Perhaps ON needs to reconsider how it uses the fields.
(Of
23 matches
Mail list logo
