Re: [Shinken-devel] Shinken 1.2.1 - Only two major issues left

Hello,
Scheduler fix is in a pull request.
I am hoping one of you can run a few tests or benchmarks to make sure it
is acting as expected.
After that, tag and release 1.2.1.
Cheers,
xkilian
On 12-09-27 10:34 PM, Francois Mikus wrote:
> Hello,
>
> To my knowledge there are only three blocking issues left:
>
> * notification issue at after a downtime expiry (Reported by a
> couple users)
> o No one has stepped up to the plate to figure it out yet. There
> are forums posts about it(monitoring.fr or shinken forums)
> * notification issue/problem with reactionner for old notifications
> (Reported by Michael Grundman, but may be related to previously
> reported issue)
> o Nap will have to tell us if/when he can look at this.
> * Making the scheduler polling recurring timing ore deterministic
> (Reported by Wh3don, patch work by Thibault Cohen with ideas and
> testing from me)
> o This one should be canned tomorrow (fingers crossed)
>
> If you see anything else that needs to be fixed urgently, especially
> user impacting, now is the time.
>
> From a planning perspective, 1.2.1 is due out, as 1.2 has a few user
> impacting bugs that need to be placed in the hands of users. Not
> everyone is happy with a broken product...
>
> Cheers and have a good friday!
>
> X
>
>
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>
>
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel

Thread view

Hi everyone,
I do not like ask that, but can someone help me to merge (or not) pull request 466 about plugin netint ? At this time, I used to work on master branch to do pull request and it is just a pain in the *** now if I want to do good pull request on separated branches.
So I wondering if we can merge this, then I will can do good separated pull requests to others things :)
Thanks.
--
*Romain Forlot*
pub 4096R/862907E5 2011-05-26
Key fingerprint = 4549 A7CA 17DC D0AA 0FE0 7953 E6A8 A0C8 8629 07E5
uid Romain Forlot <rforlot@...>
sub 4096R/153E34C2 2011-05-26

Hello,
The merge has been done. Now we just need a few users to run some blind
new install tests to make sure it is idiot proof. ;-)
Thanks for you work. If you have any pending fixes that you want to
include in 1.2.1 now is the time.
Cheers,
X
On 12-09-21 2:43 AM, Compte Yahoo wrote:
> Hi everyone,
>
> I do not like ask that, but can someone help me to merge (or not) pull request 466 about plugin netint ? At this time, I used to work on master branch to do pull request and it is just a pain in the *** now if I want to do good pull request on separated branches.
>
> So I wondering if we can merge this, then I will can do good separated pull requests to others things :)
>
> Thanks.
> --
> *Romain Forlot*
>
> pub 4096R/862907E5 2011-05-26
> Key fingerprint = 4549 A7CA 17DC D0AA 0FE0 7953 E6A8 A0C8 8629 07E5
> uid Romain Forlot <rforlot@...>
> sub 4096R/153E34C2 2011-05-26
>
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel

Hello,
To my knowledge there are only three blocking issues left:
* notification issue at after a downtime expiry (Reported by a couple
users)
o No one has stepped up to the plate to figure it out yet. There
are forums posts about it(monitoring.fr or shinken forums)
* notification issue/problem with reactionner for old notifications
(Reported by Michael Grundman, but may be related to previously
reported issue)
o Nap will have to tell us if/when he can look at this.
* Making the scheduler polling recurring timing ore deterministic
(Reported by Wh3don, patch work by Thibault Cohen with ideas and
testing from me)
o This one should be canned tomorrow (fingers crossed)
If you see anything else that needs to be fixed urgently, especially
user impacting, now is the time.
From a planning perspective, 1.2.1 is due out, as 1.2 has a few user
impacting bugs that need to be placed in the hands of users. Not
everyone is happy with a broken product...
Cheers and have a good friday!
X

On Fri, Sep 28, 2012 at 4:34 AM, Francois Mikus <fmikus@...> wrote:
> Hello,
>
> To my knowledge there are only three blocking issues left:
>
> notification issue at after a downtime expiry (Reported by a couple users)
>
> No one has stepped up to the plate to figure it out yet. There are forums
> posts about it(monitoring.fr or shinken forums)
>
> notification issue/problem with reactionner for old notifications (Reported
> by Michael Grundman, but may be related to previously reported issue)
>
> Nap will have to tell us if/when he can look at this.
>
> Making the scheduler polling recurring timing ore deterministic (Reported by
> Wh3don, patch work by Thibault Cohen with ideas and testing from me)
>
> This one should be canned tomorrow (fingers crossed)
>
> If you see anything else that needs to be fixed urgently, especially user
> impacting, now is the time.
>
> From a planning perspective, 1.2.1 is due out, as 1.2 has a few user
> impacting bugs that need to be placed in the hands of users. Not everyone is
> happy with a broken product...
>
> Cheers and have a good friday!
>
Hi,
I'll try to hunt down the first one. I just can't reproduce on unit
tests, so it will take time to reproduce and find the root cause. for
the N°2, which ticket is it?
Thanks,
Jean

Hello,
Scheduler fix is in a pull request.
I am hoping one of you can run a few tests or benchmarks to make sure it
is acting as expected.
After that, tag and release 1.2.1.
Cheers,
xkilian
On 12-09-27 10:34 PM, Francois Mikus wrote:
> Hello,
>
> To my knowledge there are only three blocking issues left:
>
> * notification issue at after a downtime expiry (Reported by a
> couple users)
> o No one has stepped up to the plate to figure it out yet. There
> are forums posts about it(monitoring.fr or shinken forums)
> * notification issue/problem with reactionner for old notifications
> (Reported by Michael Grundman, but may be related to previously
> reported issue)
> o Nap will have to tell us if/when he can look at this.
> * Making the scheduler polling recurring timing ore deterministic
> (Reported by Wh3don, patch work by Thibault Cohen with ideas and
> testing from me)
> o This one should be canned tomorrow (fingers crossed)
>
> If you see anything else that needs to be fixed urgently, especially
> user impacting, now is the time.
>
> From a planning perspective, 1.2.1 is due out, as 1.2 has a few user
> impacting bugs that need to be placed in the hands of users. Not
> everyone is happy with a broken product...
>
> Cheers and have a good friday!
>
> X
>
>
>
> ------------------------------------------------------------------------------
> Got visibility?
> Most devs has no idea what their production app looks like.
> Find out how fast your code is with AppDynamics Lite.
> http://ad.doubleclick.net/clk;262219671;13503038;y?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>
>
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@...
> https://lists.sourceforge.net/lists/listinfo/shinken-devel

On Sun, Oct 7, 2012 at 7:10 AM, Francois Mikus <fmikus@...> wrote:
> Hello,
>
> Scheduler fix is in a pull request.
>
> I am hoping one of you can run a few tests or benchmarks to make sure it is
> acting as expected.
>
> After that, tag and release 1.2.1.
>
> Cheers,
>
> xkilian
>
Hi,
The scheduling "flattening" patch is merged, so I'm tagging 1.2.1.
This version fix some of bugs, like the "too few" logging problem for
the scheduler.
Jean