Jim,
We can test on Dell(no 12Gs yet. Al Chu. has access to them), SuperMico,
Emerson, Radisys, Foritnet and Advantech.
The problem is, it takes a long time to schedule moving these computers to
the racks that where they will be tested. I can't commit to moving all that
hardware because of another constraint that JBLade and others are up
against.
September, October and the first two weeks of November are fall demo time
period. Realisticly all testing has to be done by mid August for the
companies doing DCIM/IPMI demos in the fall. I've also got the 2012 JavaOne
conference to deal with. After mid Auguest everyone(JBlade and other firms)
are on planes or new hardware has to be debugged. I've got a most 35
days(end date August 15) where we could test. I'm sure it will be a subset
of the fore mentioned hardware. Anyone have a preference on what hardware
to test ?
Hank
On Fri, Jul 6, 2012 at 5:15 PM, Jim Mankovich <jm...@hp.com> wrote:
> All,
>
> I would like to release a new version of ipmitool in the near future, and
> I have some
> questions related to releasing a new version. I can create the new
> source tar bundle
> of the new version and make it available, but I'm going to need help with
> verification
> and testing.
>
> What changes remain to be submitted to the TOB cvs repository before we
> cut the
> new release? I have one change out for review that I plan on submitting
> next week and I
> see that G has set of patches out for review as well. Is there anything
> else anyone is
> working on that they would like to see in the new release?
>
> I would like to get this release done in a timely fashion, maybe by the
> end of July, so this is
> your opportunity to speak up if you want something in this release. I
> would also like to cut
> more frequent releases of ipmitool if there is development getting done,
> so don't think of this
> release as the last chance to get new changes into a release of ipmitool
> for next few years.
>
> I think it would be reasonable to first release a beta version,
> 1.8.12beta, and then ask for
> folks to do some testing before cutting 1.8.12. I'm thinking this would
> be a good way to go
> given how much time has elapsed since the 1.8.11 release. If we a do a
> beta release first,
> then how much time would be reasonable before moving to 1.8.12? If we
> don't do a beta
> release, then we could just move on from 1.8.11 to 1.8.12 to ... as fixes
> come in that need to
> be resolved. Any preferences. I think doing the beta makes sense if
> there is some
> commitment by people to test the beta release in a timely fashion. If no
> one can help out
> with testing in the short term, then I'd prefer just cutting 1.8.12 and
> then later 1.8.13 when
> as bugs get reported and fixed.
>
> Thanks for your Support,
> Jim
>
> --
> -- Jim Mankovich | jm...@hp.com --
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Ipmitool-devel mailing list
> Ipmitool-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
