Hi Bryan,
I thought we encourage everybody to move to ipmidirect plugin.
ipmi plugin is now disabled by default.
Therefore I thought we probably will never have a fix on these bugs.
But we can also just leave them open. 
Cheers,
Uli


> -------- Original-Nachricht --------
> Datum: Mon, 13 Dec 2010 10:00:13 -0700
> Von: Bryan Sutula <[email protected]>
> An: [email protected]
> Betreff: Re: [Openhpi-devel] Bugs listed against ipmi plugin
> 
> RE:
> On Mon, 2010-12-13 at 15:38 +0100, Kleber, Ulrich (NSN - DE/Munich)
> wrote:
> > Hi, 
> > the bug tracker has still 4 bug reports open against the 
> ipmi plugin,
> > but we have a decision not to maintain that plugin anymore.
> > 
> > Therefore I suggest to reject and close all these reports:
> > 
> > 1565999         ohoi: domain not fully up, sel support = 0  
> > 1639404         Watchdog RDR not create for resource with watchdog
> > capabilit  
> > 1693130         RDRs are not being populated  
> > 3029659         IPMI: missed B.02 saHpiEventLogCapabilitiesGet
> > support  
> > 
> > Please send comments if you object to closing these reports.
> 
> Since the bugs are real and the code has not been removed, is there a
> different state for these bugs?
> 
> I still see the possibility that there are people using this plug-in,
> perhaps who are not part of this -devel list, who may wish to pick up
> support when they realize that it is going away.
> 
> Let me explain a little.  The -devel group is quite small, 
> though there
> may be a number of other observers.  OpenHPI gets picked up by several
> large distros (Red Hat, SuSE, Debian and it's derivatives) 
> and then gets
> into user hands from there.  This is a very slow process...years, in
> fact.  For example, RHEL6 just released with openhpi 2.14.1, so that
> version will be in the field for quite some time.
> 
> When the ipmi plugin disappears from these distros, users may be
> motivated to become involved in order to support what they use.  It
> would be unfortunate to just throw away the information when 
> it's really
> not causing us any problem.  So can we move these reports to 
> a different
> state or category, so that we don't have to worry about them for now?
> I'd propose closing them if/when we decide to remove the ipmi plugin
> code from the main trunk.
> 
> Best regards,
> Bryan Sutula
> 
> 
> --------------------------------------------------------------
> ----------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Openhpi-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
> 
> -- 
> GRATIS! Movie-FLAT mit über 300 Videos. 
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome
> 

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to