Hi Renier, 
        Can you ellaborate a little bit more on the redundancy that you are 
currently working on.  I would like to get more details.

Questions:

- Is there any synch data between 2 instances of OpenHpi?
- If for example, one threshold is changed in one OpenHpi when multiple OpenHpi 
are currently running?


Thanks!

Jean-Michel Audet
Kontron Canada 


-----Message d'origine-----
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Jonathan Fournier
Envoyé : Thursday, April 17, 2008 1:58 PM
À : [EMAIL PROTECTED]
Cc : [email protected]; [EMAIL PROTECTED]
Objet : Re: [Openhpi-devel] time frame for the next stable version 2.12

Hi Renier,

I didn't know you were already working on the domain redundancy, do
you need any help for testing?

Regards,

/jonathan

>
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Renier Morales
> Sent: Thursday, April 17, 2008 12:32 PM
> To: [EMAIL PROTECTED]; [email protected]
> Subject: Re: [Openhpi-devel] time frame for the next stable version 2.12
>
>
>
> [EMAIL PROTECTED] wrote on 04/17/2008 10:51:31 AM:
>
> > > In that case lets settle for the following release dates:
> > > 2.11.1 - 4/18
> > > 2.11.2 - 5/16
> > > 2.11.3 - 6/13
> > > 2.11.4 - 7/11
> > > 2.12.0 - 8/8
> > >
> > > How does that sound?
> >
>
> > Do we typically plan several interim development releases before
> > a final release?
>
> Yes.
>
> > Are there any major infrastructure changes planned that would require
> > substantial work, hence requiring multiple interim releases?
>
> The interim (development) releases are for adding new features. The 
> development releases serve as a test bed for these new features and allows 
> for stabilization time.
>
> There is one feature, discussed on the ML last year, that I'm working on for 
> 2.12.0 which changes the way domains are dealt with in order to provide some 
> redundancy:
> https://sourceforge.net/tracker/index.php?func=detail&aid=1945076&group_id=71730&atid=532254
>
> That one will need some time to stabilize. I have other features for 
> additional hardware support, but these will happen at the end of '08.
>
> > What is the planned content for these interim releases?
>
> Take a look at the SF tracker for groups 2.11.1, 2.11.2, ... etc.
> Usually, a few things get pushed to the next devel release depending on time 
> constraints, or amount of work needed to close them.
> The expectation is that as bugs are reported they will be placed in the next 
> release groups. Other bugs are just in progress (e.g. the memory leak bug, 
> looks like it might need to wait until 2.11.3).
>
> > We might be able to pitch in to help expedite the release.
>
> So I assume the plan above is not soon enough for you. When do you need a 
> stable release?
>
>         --Renier
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to