Re: [tools-discuss] Re: webrev updates

2006-07-26 Thread Dan Price
On Wed 26 Jul 2006 at 03:09PM, Stacey Marshall wrote: > Hmm, > > from home I found my suggested fix for the Next Prev. buttons did not work > and I have thus had > to revert back to: > > parent.lhs.location.replace(parent.lhs.location.pathname + "#" + num); > parent.rhs.location.repl

[tools-discuss] Re: webrev updates

2006-07-26 Thread Stacey Marshall
Hmm, from home I found my suggested fix for the Next Prev. buttons did not work and I have thus had to revert back to: parent.lhs.location.replace(parent.lhs.location.pathname + "#" + num); parent.rhs.location.replace(parent.rhs.location.pathname + "#" + num); To have both the b

Re: [tools-discuss] Project bug tracking needs

2006-07-26 Thread Valerie Anne Bubb
On Wed, 26 Jul 2006, Scott Rotondo wrote: John Levon wrote: On Tue, Jul 25, 2006 at 05:42:35PM -0700, Stephen Hahn wrote: frustrated with tracking integrations for Zones. We ended up tracking 1464 project bugs on SMF during its development...** And a non-trivial number of those not req

Re: [tools-discuss] Project bug tracking needs

2006-07-26 Thread Richard Lowe
Scott Rotondo wrote: John Levon wrote: [snip] The problem as I see it was using the "official" category rather than what we use: development/kernel/xen Yes, it's very important to keep the development bugs (which are found and fixed in a project-private workspace before integration) se

Re: [tools-discuss] Project bug tracking needs

2006-07-26 Thread Scott Rotondo
John Levon wrote: On Tue, Jul 25, 2006 at 05:42:35PM -0700, Stephen Hahn wrote: frustrated with tracking integrations for Zones. We ended up tracking 1464 project bugs on SMF during its development...** And a non-trivial number of those not required to be fixed for integration ended up i

[tools-discuss] Re: webrev updates

2006-07-26 Thread Stacey Marshall
Hi Daniel, Perhaps others have commented, I don't see the replies on the thread! Certainly like the idea of placing the specific SCCS comments at the top of each page and providing the PDF file (something I create separately). The idea of creating a patch is novel too. With regard to the 'Fra

Re: [tools-discuss] Project bug tracking needs

2006-07-26 Thread John Levon
On Tue, Jul 25, 2006 at 05:42:35PM -0700, Stephen Hahn wrote: > frustrated with tracking integrations for Zones. We ended up tracking > 1464 project bugs on SMF during its development...** And a non-trivial number of those not required to be fixed for integration ended up in bugster: thus th

Re: [tools-discuss] webrev updates

2006-07-26 Thread John Levon
On Wed, Jul 19, 2006 at 05:08:57PM -0700, Dan Price wrote: > http://cr.grommit.com/~dp/webrev.1/ Could the patch be "zones-fixes.diff" instead of just "patch"? regards john ___ tools-discuss mailing list tools-discuss@opensolaris.org

Re: [tools-discuss] Project bug tracking needs

2006-07-26 Thread Martin Man
Hi all, I suppose the criteria number 1 would be that the code must be open, if not than I have been said that FoxBugz[1] is ubercool. Apart from bugzilla that I consider rock solid and working and generally good choice I'd deploy trac[2] today because it does more than bug tracking, namely