Hi Michael, yes, Anton is right. I plan changes for 2.15.0 only for the clients hpitop, hpitree, etc. So no changes to main code. But I wanted to introduce the -D option for all clients, so it is some editing work to do, which I could do easily till next Monday - if I don't find other problems. I sometimes find options that are implemtented but not documented in the usage or man. So I try to fix that, too. And yesterday I started on hpiinv and got the feeling that -v doesn't work properly. Somehow the output without -v seems more verbose than with the option.
I didn't do checkin on svn yet. Is it easy to do or can I send you a patch or tar instead? The changes are not big and can still be done using patch (~ 80 lines per client). Cheers, Uli > -----Original Message----- > From: ext Bishop, Michael (ISB Linux/Telco) > [mailto:[email protected]] > Sent: Tuesday, June 08, 2010 7:16 PM > To: '[email protected]' > Subject: Re: [Openhpi-devel] [ openhpi-Bugs-3011456 ] Domain > Support forClients > > Anton - > > Thanks for clarifying. I would still like to hear from Uli > on his view of getting this work done in time for 2.15.0. > > --michael > > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > Sent: Tuesday, June 08, 2010 11:01 AM > > To: [email protected] > > Subject: Re: [Openhpi-devel] [ openhpi-Bugs-3011456 ] Domain Support > > forClients > > > > > > Michael, > > > > I guess we decided to split this bussiness into several steps. > > The first one (which I believe will go into 2.15.0) is to > > add -D parameter in OpenHPI clients (hpitop, hpitree ...). > > So base library, daemon and plug-ins will be intact. > > > > Anton Pak > > > > > Uli - > > > > > > The plan is to start the release cycle as soon as Lars is > done with > > > merging his dynamic_simulator on top-of-trunk. Roughly, > > we would freeze > > > the top-of-trunk on Monday, June 14 - and start the release > > cycle. That > > > date can be push out a bit (maybe by a week) - but it is a > > bit concerning > > > to me that we are adding significant new code right at the > > last minute. > > > We've known about the new simulator for some time - but the > > addition of > > > domain support is fairly new. > > > > > > So the key question is: How close are you to having all of > > your domain > > > support code checked-in and fully unit-tested by June 14? > > > > > > I would also highly recommend that prior to checking in the > > domain support > > > code to top-of-trunk, that you run the hpitest-3.1.1 > > conformance tests to > > > see if there is any regression in OpenHPI. The hpitest is > > one of the key > > > metrics we use for checking overall OpenHPI quality prior > > to a release. > > > We've been running this metric extensively on Lars' > > simulator to make sure > > > we're not breaking anything by adding his plugin - and so > > far those tests > > > look good. So assuming his merge goes okay - we're in good > > shape on his > > > plugin. However, on the new domain support - because I am > > less familiar > > > with it - I'm less certain of how this will affect the > > stability of the > > > release. In other words, what is your confidence level > that the new > > > domain support code will not break existing OpenHPI functionality? > > > > > > --michael > > > > > > Regards, > > > Michael Bishop > > > Enterprise Servers and Storage (ISB Linux/Telco) > > > Hewlett-Packard Company > > > 3404 E. Harmony Rd. Bldg. 5L, Post B7, Mailstop 42 > > > Fort Collins, CO 80528-9599 > > > Phone: 970-898-4393 > > > E-Mail: [email protected] > > > > > > > > >> -----Original Message----- > > >> From: Kleber, Ulrich (NSN - DE/Munich) > > [mailto:[email protected]] > > >> Sent: Monday, June 07, 2010 11:49 PM > > >> To: Bishop, Michael (ISB Linux/Telco) > > >> Cc: [email protected] > > >> Subject: RE: [Openhpi-devel] [ openhpi-Bugs-3011456 ] > > Domain Support > > >> forClients > > >> > > >> > > >> Hi, > > >> I would very much like to contribute this domain support for > > >> 2.15.0. I am currently working on the other clients and need > > >> to check things like man pages. > > >> But I need also to that company internal process clarification, > > >> before I can send the final patch. I hope to get that within > > >> this week. > > >> When do you need the final patch? > > >> Cheers, > > >> Uli > > >> > > >> > > >> > -----Original Message----- > > >> > From: ext Bishop, Michael (ISB Linux/Telco) > > >> > [mailto:[email protected]] > > >> > Sent: Monday, June 07, 2010 11:13 PM > > >> > To: Kleber, Ulrich (NSN - DE/Munich) > > >> > Cc: '[email protected]' > > >> > Subject: RE: [Openhpi-devel] [ openhpi-Bugs-3011456 ] Domain > > >> > Support forClients > > >> > > > >> > Uli - > > >> > > > >> > I'm wondering what your plans are with respect to submitting > > >> > code for Domain Support for clients? > > >> > > > >> > We're waiting on Lars Wetzel to finish up his work on the > > >> > dynamic_simulator - once he gets the go-ahead from you to > > >> > merge his branch with top-of-trunk. After the merge, the > > >> > plan was to start the 2.15.0 release cycle - which should > > >> > take 2 to 3 weeks - during which time only bug-fixes would be > > >> > allowed on the top-of-trunk. Would a later release cycle > > >> > (e.g., 2.15.1 or 2.16.0) accomodate your changes for Domain > > >> > Support in the HPI clients? > > >> > > > >> > Note to all: I will be out of the office the week of June > > >> > 21-25 - but the testing of 2.15.0 can proceed during this > > >> > time. The release would occur after I return on June 28. > > >> > > > >> > --michael > > >> > > > >> > Regards, > > >> > Michael Bishop > > >> > Enterprise Servers and Storage (ISB Linux/Telco) > > >> > Hewlett-Packard Company > > >> > 3404 E. Harmony Rd. Bldg. 5L, Post B7, Mailstop 42 > > >> > Fort Collins, CO 80528-9599 > > >> > Phone: 970-898-4393 > > >> > E-Mail: [email protected] > > >> > > > > > > > > > -------------------------------------------------------------- > > ---------------- > > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > > lucky parental unit. See the prize list and enter to win: > > > http://p.sf.net/sfu/thinkgeek-promo > > > _______________________________________________ > > > Openhpi-devel mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > > > > > > > > > > > -------------------------------------------------------------- > > ---------------- > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > lucky parental unit. See the prize list and enter to win: > > http://p.sf.net/sfu/thinkgeek-promo > > _______________________________________________ > > Openhpi-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > > > > -------------------------------------------------------------- > ---------------- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Openhpi-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
